Re: [ee4j-pmc] Migration to Jakarta installation of Nexus

[Scott Stark <starksm64@xxxxxxxxx>]

Shouldn't existing builds be able to see the 1.0.6 parent pom when building in the CI environment? The dependency-injection poms only reference the org.eclipse.ee4j:project parent pom for the release and staging repository information. As far as I know there is not anything in the CDI CI environment settings.xml that overrides this, but when I'm trying a testbuild of the api project with the following parent:

<parent>
  <groupId>org.eclipse.ee4j</groupId>
  <artifactId>project</artifactId>
  <version>1.0.6</version>
  <relativePath />
</parent>

the build is not able to resolve that parent.

On Wed, Jan 15, 2020 at 1:22 AM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Yes, we're in a transitional state.

The new parent pom hasn't been published yet.

You should still be able to deploy to oss.sonatype.org; that access isn't supposed to be removed until tomorrow (Jan 15).

But, rather than moving backwards and trying to fix that, I think we should keep moving forwards and fix it as necessary with the new Nexus at jakarta.oss.sonatype.org.