1.0.19 release points to non-existent 3.26.1-01 nexus repository manager version

[nblair]

• What are you trying to do?

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:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] org.sonatype.nexus.plugins:nexus-blobstore-google-cloud-parent 0.16.0-SNAPSHOT SUCCESS [  4.153 s]
[INFO] org.sonatype.nexus.plugins:nexus-blobstore-google-cloud SUCCESS [ 21.164 s]
[INFO] org.sonatype.nexus.plugins:nexus-blobstore-google-cloud-it 0.16.0-SNAPSHOT FAILURE [  4.945 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 44.323 s
[INFO] Finished at: 2020-08-20T21:21:01Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project nexus-blobstore-google-cloud-it: Could not resolve dependencies for project org.sonatype.nexus.plugins:nexus-blobstore-google-cloud-it:jar:0.16.0-SNAPSHOT: Failed to collect dependencies at org.sonatype.nexus.assemblies:nexus-base-template:zip:3.26.1-02 -> org.sonatype.nexus.assemblies:nexus-community-feature:xml:features:3.26.1-02 -> org.sonatype.nexus.plugins:nexus-repository-helm:xml:features:1.0.19: Failed to read artifact descriptor for org.sonatype.nexus.plugins:nexus-repository-helm:xml:features:1.0.19: Could not find artifact org.sonatype.nexus.plugins:nexus-plugins:pom:3.26.1-01 in rso-public-grid (https://repository.sonatype.org/content/groups/sonatype-public-grid/) -> [Help 1]

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.

• What feature or behavior is this required for?

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.

• How could we solve this issue? (Not knowing is okay!)

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.

• Anything else?

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!

[nblair]

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.

[mlukaretkyi]

@nblair Looks like will not be relevant, by the cause that helm source code gonna move to nexus. Helm will be removed from CircleCI.