All,
Here is our exact status.
- At 7:50am Pacific yesterday Terry was given the go-ahead by me here on this list on this thread
- At 9:55am Pacific there was a HEADS UP email by Dmitry indicating there would not be a go-head till the 15.
Unfortunately yesterday there were several private threads started that confused the situation.
We are in mid transition.
At this point we need to let Terry work and not bombard him with "why doesn't it work" questions. We need to get him a day of quiet so he can finish the process that was started at 7:50 am yesterday.
DO NOT respond on any private threads or start new public threads. Terry, if you get any offline communication, ignore it.
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.
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.
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
