> Are any of the above definitely NOT going to make another release
> using the same groupId?
commons-discovery I think is one of these
> This could be because:
> [X] the component is dormant, or
> [ ] future releases will use a groupId of o.a.c (and change package name!).
no more reasons to ma
On Thu, Aug 16, 2012 at 7:23 PM, sebb wrote:
> For components which use a Maven groupId starting with
> "org.apache.commons.", Maven deployment is already enabled via Nexus.
>
> There are a few components which still use a Maven groupId of the form
> "commons-".
> Some of these are already enabled
For components which use a Maven groupId starting with
"org.apache.commons.", Maven deployment is already enabled via Nexus.
There are a few components which still use a Maven groupId of the form
"commons-".
Some of these are already enabled in Nexus.
Nexus infra have stated that it is just as mu
