Smart proxy in Nexus Repository manager 2 was very straightforward according to this documentation.
It isn't the case in Nexus Repository manager 3 any more, and there's only a minimal amount of information regrading to the smart proxy feature in the version 3 documentation. There is also no sigh that the feature is available in the capabilities list.
Any idea how this should be configured?
Just confirmed by sonatype that this is not implemented in Nexus 3 and will be replaced by new function called Component Fabric
Details written in Nexus Repository Manager Feature Compatibility Matrix.
Related
Previously I created a maven(hosted) nexus repository for my project. Named as "project-name-private"; and for version policy, I choose category "Release".
Now project members has new requirement to update the repository name as "project-name-dependency", and version policy should be expected as "mixed".
But I could not update those value from web repository settings, because those options are gray and they are not editable.
I had installed nexus repository manager 3.01-01, and I also have Admin Account/Password.
I do not want to create new repository directly because there were already artifacts had uploaded in current repository, how could I fulfill project requirement to update the existed repository? expected to get your reply. thanks.
That is currently not possible in Nexus Repository 3.x through the UI/a supported manner.
Please file an issue here and let us know your interest in that functionality: https://issues.sonatype.org/browse/NEXUS
I would like to change the webapp context of a Nexus OSS 3 installation to run on http://localhost:8081/nexus instead of http://localhost:8081.
The documentation for version 2 is quite clear about how to do it, but the documentation for version 3 redirects to this link to configure a Nexus "capability", which mentions that
The repository manager only uses this value to construct absolute URLs to your user interface inside of email notifications.
I'm not sure then that it's the correct option. And if it is, what value should I put? /nexus or full url https://serverPublicName/nexus?
OK next time i will read documentation more carefully...
https://books.sonatype.com/nexus-book/3.0/reference/install.html#config-context-path
8-s
In Nexus 2.11.4-01 I am able to specify Base Url in Application Server Settings.
Where do I specify Base Url in Nexus Repository Manager 3.0 (Milestone 7 Release)?
Go to "administration/capabilities", then click on "create capability", and you'll see it there.
Note that this functionality was hidden under capabilities because it isn't needed in almost all cases.
I am working on a Java solution which integrates with CMIS repositories. Having chosen OpenCMIS as my open source library, am trying to ensure all test scenarios are covered. I have explored few of the repositories (Alfresco, Chemistry InMemory, Chemistry Fileshare, OpenKM) and none of them seem to provide multiple repositories which I feel is required to be covered as a part of my testing.
Being more specific with the code, below works well with almost all repositories.
Repository soleRepository = sessionFactory.getRepositories(parameter).get(0);
But I want to know if any repository supports (or can be configured to support) this code:
sessionFactory.getRepositories(parameter).get(1)
There are many CMIS servers supporting more than one repository. SharePoint, FileNet, SAP Mobile Documents, ...
Even the OpenCMIS FileShare server supports more than one repository if you configure it. Just add the following lines to your repository.properties file and it will expose second repository:
repository.second = {user.home}
repository.second.readwrite = test, cmisuser
repository.second.readonly = reader
I have a number of hosted and proxy repositories carried in my Nexus 1.9.1.1 instance.
From what I have read, re-indexing ("Update Index") should generate the archetype-catalog.xml file with the proper contents.
No matter what though, my archetype-catalog.xml's continue to be essentially "0-sized" (they have the xml headers, etc, but no archetypes.)
In one particular case, where I am proxying another repo and that repo has a plus-sized archetype-catalog, mine continues to show 0 elements.
Adoption of the centralized repo is taking heat because other developers can't create projects using their favorite archetypes. Any thoughts?
Thanks!
-Lorin
Change the pom.xml for the archetype so that it has:
<packaging>maven-archetype</packaging>
#Croesus's answer is a step in the right direction, but a more complete solution is described in the Maven archetype documentation.