[jboss-dev] Release jboss-common-core 2.2.5.GA for JBCOMMON-48

[Dimitris Andreadis]

AS trunk now uses jboss-common-core 2.2.5.GA:
http://jira.jboss.com/jira/browse/JBAS-5351

I've also cleaned-up the jboss logging project.

It's now at
org.jboss.logging:jboss-logging-spi:2.0.5.GA
org.jboss.logging:jboss-logging-jdk:2.0.5.GA
org.jboss.logging:jboss-logging-log4j:2.0.5.GA

AS trunk imports those latest releases.

When releasing other jboss projects, you may want to point to those instead, and if you want 
to open JIRAs against jboss logging, please use: http://jira.jboss.com/jira/browse/JBLOGGING

While there, I can see AS trunk bringing in unused dependencies, e.g. older releases of 
common-core. However this doesn't seem to pose a problem because those are not referenced by 
the build and the correct version ends up being used.


Scott Stark wrote:
> I have updated trunk to jboss-common-core 2.2.5.beta1 in 
> component-matrix/pom.xml. This includes JBCOMMON-48 and JBCOMMON-49 for 
> the serialVersionUID issue.
> 
> Scott Stark wrote:
>> I want to release jboss-common-core 2.2.5.GA and update jbossas to use 
>> this to pickup the fix for:
>> http://jira.jboss.com/jira/browse/JBCOMMON-48
>>
>> Without this we can't use vfs* urls in systemIds passed to the 
>> JBossEntityResolver. An example of where this is needed was posted on 
>> the security design forum.
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development