I am going to upgrade Nexus 2 to Nexus 3 and have read the documentation about upgrading to Nexus 3.2 and it only mention using the upgrade wizard.
is it possible to do the same thing by writing a script or using some command line tool? I am going to upgrade several nexus installations and if it where possible to do it using a script it would save me a lot of time.
Update:
I have gotten response from Sonatype that there is no command line / REST interface that you can use to migrate from Nexus 2 to Nexus 3. You need to use the GUI migration wizard.
Related
I'm having an issue with a netcoreapp project that's running 2.2. In Microsoft Azure the 2 supported versions are 2.1 and 3.1, both will require some serious migrating. Is it possible to install 2.2 on the server?
Your best option would be to deploy a self-contained application. You can do so by running
dotnet publish -r <RID> --self-contained
In this way you will cut loose the depedency on the supported runtimes from Azure side.
There is of course the downside (as always) that your applications would be bigger by roughly 100Mb
I am trying to move all repositories I am using to Nexus 3. I use Apache Archiva as a Maven repository. I read that it's possible to copy repos between Archiva and Nexus 2. Is there any way to do the same with Nexus 3 ?
I have tried to do a workaround and succeeded. I created an instance of Nexus2 and migrated Archiva there. After that I have used the upgrade agent from Capabilities to migrate from Nexus2 to 3. Not a complicated way and is fast as well.
I'm currently use OpenDJ 2.6.4 in Suse Linux 11 and my goal is to upgraded to Directory Services 6.5.
From what I read, especialy on Chapter 9. Before You Upgrade
and Chapter 10. Upgrading a Directory Server, the process seems pretty simple, i.e, after checking Java version, backup and disable stuff we just need to execute the upgrade command.
This process run well or it's harder as it look?
From what I read on several release notes, i don't expect to have big changes on my current web application, is that right?
That is correct, there should be no change to the applications (since the interface is standard LDAPv3).
If your OpenDS service is replicated, you can upgrade one server after another, with zero downtime for the overall service.
When upgrading from 2.6, you will probably need to upgrade the Java runtime as well, since DS 6.5 requires Java 8 (and also supports 11).
So, stop a server, backup the whole server, unzip DS 6.5, upgrade Java to 8+, run upgrade, start-ds.
You might want to test the upgrade process on a dev environment. If you don’t have a dev env yet, you can create one by just copying the whole OpenDJ 2.6.4 directory and databases to a different location or another server.
I operate some Docker services. Some of them are selfmade with Dockerfiles. I now want to store them into a Sonatype Nexus private repository to publish them to another server in my network.
My research half a year ago gave me Nexus 2 OSS as best option. But now Nexus 3 got released and I'm kinda confused. What version should I use? Greatest confusion is because there is no difference between Pro and OSS version anymore on Docker Hub:
sonatype/nexus has got tags oss and pro
sonatype/nexus3 has only got tags like 3.x.x
Question is: May I use Nexus 3 for free? Or will there be any costs as in Nexus 2 Pro?
Nexus Repository Manager 2 does not support Docker as a format. Nexus Repository Manager 3 does, and Docker support is a part of our OSS solution, meaning you can use Docker completely free. There is a professional version coming with 3.1 that will start to have features such as high availability, expanded enterprise support, as well as just regular support of the product.
As for the Docker images, Nexus 3 now has the ability to operate as OSS or Pro from the same bundle so you'll likely only see tags for Releases, not OSS and Pro.
I have a web application which is entirely .net 3.5. I have created a Setup project using the wizard making sure that I selected 3.5 from the targeted famework.
When I have built the setup.exe and the Windows Installer Package and I have tried to install it on a test machine it prompts straight away to download and install the .net framework 4 client profile first.
The end-user doesn't want to upgrade their servers at this time to the latest version of .net.
Any suggestions?
Double click the .msi file, seems to be installing properly. I would also like to know how to avoid this.