Open nblair opened 4 years ago
I've come up with a temporary workaround for my plugin, the solution is to exclude the community assemblies in the pom for my plugin's -it module, like so:
<dependency>
<groupId>org.sonatype.nexus.assemblies</groupId>
<artifactId>nexus-base-template</artifactId>
<version>${nxrm-version}</version>
<type>zip</type>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>org.sonatype.nexus.assemblies</groupId>
<artifactId>nexus-community-feature</artifactId>
</exclusion>
<exclusion>
<groupId>org.sonatype.nexus.assemblies</groupId>
<artifactId>nexus-cma-community</artifactId>
</exclusion>
</exclusions>
</dependency>
With this change, the -it module of my plugin builds successfully in CircleCI.
@nblair Looks like will not be relevant, by the cause that helm source code gonna move to nexus. Helm will be removed from CircleCI.
I'm the author of another plugin in the community currently in the process of updating the plugin to the latest version of Nexus Repository Manager (3.26.1-02).
I'm running into repeated failure to build my project only on CircleCI, relevant section:
Note: those that can access internal Sonatype infrastructure will not see this same error; to reproduce you have to have an agent that is not authenticated to internal repositories.
Plugins that use the common multi-module pattern with an
-it
module pull in the nexus-base-template, which now references public releases of the nexus-repository-helm project.I believe another release of the nexus-repository-helm to support 3.26.1-02 is required. In https://github.com/sonatype-nexus-community/nexus-repository-helm/commit/4cdcb80adf4e27e80f17ec28cc68c64fc5497059#diff-600376dffeb79835ede4a0b285078036R52 the
nxrm-version
property is set to 3.26.1-01. That release is not visible to the public, only 3.26.1-02 is.It looks like master has already moved to 3.27 - is there a way to branch off of the 1.0.19 tag and publish a 1.0.19.1 tag?
Thanks!