Differences between revisions 1 and 2
Revision 1 as of 2010-07-14 19:05:51
Size: 2239
Editor: sebbapache
Comment: GroupIds and Nexus plans
Revision 2 as of 2017-03-30 16:30:43
Size: 2350
Editor: sebbapache
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

'''Note that the groupId can only be changed if the Java package is also changed; see MavenAndClassPath'''.

Commons GroupIds

Many Commons components have migrated to the Maven groupId org.apache.commons, but some are still using groupIds of the form commons-<component>.

Note that the groupId can only be changed if the Java package is also changed; see MavenAndClassPath.

This page records which components still use their own groupIds, and whether there are any plans to migrate to org.apache.commons or not.

Component

Nexus-enabled?

Migration Plan

beanutils

betwixt

chain

cli

YES

codec

collections

configuration

dbcp

dbutils

digester

discovery

el

fileupload

httpclient

NOT NECESSARY

No more releases will be made; see http://hc.apache.org/ instead

io

jxpath

lang

launcher

logging

Unlikely to be any more releases

modeler

net

Could migrate at version 3.0 ?

pool

primitives

scxml

validator

CommonsGroupids (last edited 2017-04-21 13:13:03 by sebbapache)