Makes sense. I believe we’re going to go with the approach we have now where Content Selectors are on the individual company-maven-hosted repositories (where the total contents will be small) and require that each company ensure they update their settings.xml file to include this secondary repository. Requiring that the Nexus Admin knows each and every single dependency that needs to be kept private would be a cumbersome task.
1 Like