[jboss-dev] JBossCommon tidy up

[Scott M Stark]

We need to be careful about leaking java5 features into the 1.x branch
as this is the basis for 4.0.x cps. For 4.2.x I think we should branch
the current common trunk modules to create a 2.0 branch so that we don't
have unintended changes going into a common stream going into 4.2.x.

Dimitris Andreadis wrote:
> A reminder when you update JBoss Common to create JIRA tasks to track
> the changes:
> http://jira.jboss.com/jira/browse/JBCOMMON
> 
> There is the old "legacy" jboss common that seperated from the jbossAS
> code:
> https://svn.jboss.org/repos/common/common-old/branches/Branch_1_0/
> 
> This produces the 1.x common libs used by JBoss 4.x
> 
> In repository.jboss.com this is:
> jboss/common
> 
> Then there is the "new" common, used by jboss HEAD, and probably
> elsewhere:
> 
> https://svn.jboss.org/repos/common/build/trunk/
> https://svn.jboss.org/repos/common/common-core/trunk/
> https://svn.jboss.org/repos/common/common-logging-spi/trunk/
> https://svn.jboss.org/repos/common/common-logging-jdk/trunk/
> https://svn.jboss.org/repos/common/common-logging-log4j/trunk/
> 
> In repository.jboss.com this is
> Jboss/common-core
> Jboss/common-logging-spi
> Jboss/common-logging-jdk
> Jboss/common-logging-log4j
> 
> There is a jboss/common/snapshot leftover version that I'm going to
> remove, unless someone objects. If you need a jboss-common 1.0 snapshot,
> this is stored in jboss/common/snapshot-Branch_1_0.
> 
> Same goes for jboss/common-**/1.0. The common-** should only produce 2.x
> versions.
> 
> Cheers
> /Dimitris
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development