I am trying to upgrade Sonatype Nexus 2.14 to latest 3.41.
Current Directory Structure /opt/nexus2/nexus2.14, sonatype-work.
My question is if i want to extract the latest version 3.41 should i do it in /opt/nexus2 ( its will then not create new sonatype-work as its already there) or should i make a new directory for it.
If not then it will look like this /opt/nexus2/nexus2.14, nexsu3.41, sonatype-work,
If yes then it will look like this /op/nexus2/nexus2.14 sonatype-work &
/opt/nexus3/nexus3.41 sonatype-work
..
after installing nexus3.41 i will migrate all the work form nexus 2 to nexus 3 using GUI.
It isn’t an “upgrade”, it is a migration. See here:
https://help.sonatype.com/display/NXRM3/Upgrade+Procedures
The procedure outlined in that help document will import all the configuration and data from Nexus Repo 2 into a new Nexus Repo 3 instance. When finished, your original Nexus Repo 2 will still be intact, and you’ll have a new Nexus Repo 3 instance. Nexus Repo 2 and 3 should not be sharing the same work directory, make a new install location for the Nexus Repo 3 install and its work directory.
Related
I have two npm packages that are private repositories hosted on gitlab.com under a group organization.
My first package lives well and get updated and downloaded by users of the same organisation.
To install a private scoped package, the doc says:
# Set URL for your scoped packages.
# For example package with name `#foo/bar` will use this URL for download
npm config set #foo:registry https://gitlab.example.com/api/v4/projects/<your_project_id>/packages/npm/
So my .npmrc looked like
#mygroup:registry=https://gitlab.com/api/v4/projects/<id-project-1>/packages/npm/
//gitlab.com/api/v4/projects/<id-project-1>/packages/npm/:_authToken=<token>
//gitlab.com/api/v4/projects/<id-project-2>/packages/npm/:_authToken=<token>
//gitlab.com/api/v4/packages/npm/:_authToken=<token>
Obviously, everything works fine for the first package but not for the second one.
What I can't understand is why a scoped package should refer to a unique project url?
Because of this, I can't install both of my packages: the url of my scoped packages will only be valid for one of them.
I looked at the api endpoint to return a list of my group's packages I found this:
https://docs.gitlab.com/ee/api/packages.html#within-a-group
So I updated my .npmrc to
#mygroup:registry=https://gitlab.com/api/v4/groups/mygroup/packages/npm/
//gitlab.com/api/v4/projects/<id-project-1>/packages/npm/:_authToken=<token>
//gitlab.com/api/v4/projects/<id-project-2>/packages/npm/:_authToken=<token>
//gitlab.com/api/v4/packages/npm/:_authToken=<token>
But it doesn't work.
On the group/group-id/packages route I only get gitlab infos but nothing in an npm friendly format.
How to install more than one private scoped npm package hosted under the same group?
The instance level endpoint seems answer to your situation instance-level-npm-endpoint
Using:
npm config set #mygroup:registry https://gitlab.example.com/api/v4/packages/npm/
npm config set -- '//gitlab.example.com/api/v4/packages/npm/:_authToken' "<your_token>"
You should be able to publish #mygroup/project1 & #mygroup/project2
I experienced some troubles using yarn (1.22.10) so I'll post more details here just to save couple of hours to anybody reading this.
For some unknown reasons I was able to install the package with npm but not with yarn and I got Request failed \"404 Not Found\"
I ended up by creating a .npmrc file at the root of the project (I'm working with docker) with the following content:
#my-org:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=<GITLAB_TOKEN_API_SCOPE>
//gitlab.com/api/v4/projects/<ID_PROJECT_1>/packages/npm/:_authToken=<GITLAB_TOKEN_API_SCOPE>
//gitlab.com/api/v4/projects/<ID_PROJECT_2>/packages/npm/:_authToken=<GITLAB_TOKEN_API_SCOPE>
Line 3 and 4 are required for yarn but not for npm.
To make it work replace #my-org by your gitlab organisation name, gitlab.com by the url where your projects are, <ID_PROJECT_X> by the ids of the projects you want to install and <GITLAB_TOKEN_API_SCOPE> by a personal token with an API scope.
I am trying to install JD-Eclipse plugin in IBM Rational Application Developer Version: 9.5.0.2 . Followed the steps provided in link http://jd.benow.ca/ using Install New Software option in RAD. Getting below exception while installing,
An error occurred while collecting items to be installed
session context was:(profile=IBM Software Delivery Platform com.ibm.sdp.eclipse.ide, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.ibm.java.diagnostics.common.datamodel.impl.gui,3.0.12.201611250914
No repository found containing: osgi.bundle,com.ibm.java.diagnostics.common.extensions.gui,3.0.12.201611250914
No repository found containing: osgi.bundle,com.ibm.java.diagnostics.healthcenter.coredisplayers,3.0.12.201611250914
No repository found containing: osgi.bundle,com.ibm.java.diagnostics.healthcenter.gui,3.0.12.201611250914
No repository found containing: osgi.bundle,com.ibm.java.diagnostics.healthcenter.integration,3.0.12.201611250914
No repository found containing: osgi.bundle,org.apache.batik.dom,1.6.0.v201011041432
No repository found containing: org.eclipse.update.feature,org.eclipse.birt.report.designer.editor.xml.wtp,4.4.2.v201410272105-8F9F7cFT0z0-TRNfUodYol
No repository found containing: osgi.bundle,org.eclipse.birt.report.designer.ui.editor.xml.wtp,4.4.2.v201410272105
Please help me out on this issue
Plugin install issue got resolved by below step
Go to Help → Install new software → Here uncheck “Contact all update sites during install to find required software”
Try Running RAD as Admin. It solved it for me
I am using api-ldap-client-all-1.0.0-M28.jar as maven dependency in my project. Now api-ldap-client-all-1.0.0-M28.jar internally uses mina-core 2.0.7 version which has 100% CPU usage issues (DIRMINA-988, DIRMINA-1001) which are resolved in latest version(2.0.13) of mina-core. Now I want to update api-ldap-client-all-1.0.0-M28.jar with mina-core 2.0.13. What will be the procedure to do that?
As per Stanbol documentation, I've checked-out source code (% svn co http://svn.apache.org/repos/asf/stanbol/trunk stanbol) and after did maven build. All is fine. Now I've started executable jar (org.apache.stanbol.launchers.full-1.0.0-SNAPSHOT).
After starting this I do not see any menu option to open CMSAdapter and contenthub. I can only see /enhancer, /topic, /entityhub, /sparql, /ontonet, /rules, and /reasoners in the menu option.
Here is the localhost page -
When I saw the checked-out directory then I did not find folders corresponding to cmsadpater and contenthub.
After I tried to download complete zip from source again and now i can see cmsadpater and contenthub -
But I'm getting error during build.
Please suggest what I'm missing here.
[ERROR] Failed to execute goal on project org.apache.stanbol.launchers.full: Could not resolve dependencies for project org.apache.stanbol:org.apache.stanbol.launchers.full:jar:0.12.0: Failure to find org.apache.sling:org.apache.sling.launchpad:xml:bundlelist:8 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
ContentHub and CMSAdapter components have been discontinued from version 1.x. You can still find them at 0.12.x branch (https://svn.apache.org/repos/asf/stanbol/branches/release-0.12/)
Hope that helps
Say I have two repos: repoa and repob. I installed a package 3.1 ver from repoa. I have a newer version 3.2 in repob.
How could I upgrade the package from repob? I tried to yum upgrade, but looks it always stick to the original repo - repoa, and didn't look at the package in repob at all. I can use 'yum provides' to get the package information from two repose, but only repoa looks recognised.
I tried several things such as change the priority higher for repob, temporarily remove the repoa, but none of them working.
I guess I need to remove it then do reinstallation from repob.