Re: [ee4j-build] Missing artifacts in OSSRH staging

[Tomas Kraus <tomas.kraus@xxxxxxxxxx>]

Yes, this will solve this OSSRH staging nightmare at least for some 
projects.

But do we have some projects that are integrated in GF and we are sure 
that TCK/CTS passed with them?


Tomas

Dne 04.01.19 v 1:47 Bill Shannon napsal(a):

> Ed Bratt wrote on 1/3/19 3:56 PM> Another suggestion might be that we start
> promoting components that are ready,
> > over to Maven Central -- API JARs that have been tested and confirmed working
> > might be the first set of components that can be promoted in preparation for
> > final release. There might be other project artifacts that could be considered
> > ready to release.
> YES!!!
>
> If the component has completed its Eclipse Release Review, and has been tested
> with the TCK and CTS, it should just be released to Maven Central.  There's no
> reason to wait around for the rest of GlassFish.