On Thu, Aug 16, 2012 at 7:23 PM, sebb <seb...@gmail.com> 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-<component>". > Some of these are already enabled in Nexus. > > Nexus infra have stated that it is just as much work to enable one > component as enabling lots, so I said I would ask Commons which > components still need to be enabled. > > So hopefully we can put together a list of components that need to be > enabled in Nexus and ask for these all to be done at once. > > The following are not (yet) in Nexus > > commons-beanutils > commons-betwixt > commons-collections > commons-discovery > commons-el > commons-jxpath > commons-launcher > commons-logging > commons-modeler > commons-primitives > commons-scxml > > Are any of the above definitely NOT going to make another release > using the same groupId? > This could be because: > - the component is dormant, or > - future releases will use a groupId of o.a.c (and change package name!). > <snip/>
Hard to say about commons-scxml, so suggest keeping in the list for Nexus infra. -Rahul > The following are now using o.a.c for trunk releases: > > commons-digester (2.x) > commons-lang (2.x) > commons-dbcp (1.x) > > It seems very unlikely that another digester 2.x release will ever be > needed, and probably not LANG 2.x, but what about DBCP? > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
