[jboss-dev] org.jboss:javassist or javassist:javassist

[Kabir Khan]

I think Paul is the main person maintaining javassist in maven
On 27 May 2008, at 13:41, Dimitris Andreadis wrote:

> The problem is the same artifacts are uploaded by different people  
> in different places.
>
> Paul has created this page:
> http://wiki.jboss.org/wiki/MavenProjectNaming
>
> javassist:javassist seems like a better choice in this case. Why not  
> asking Chiba?
>
> What's this 'banned dependency list' ?
>
> Carlo de Wolf wrote:
>> What's it going to be?
>> Now I have org.hibernate:hibernate-annotations:3.3.1.GA declaring a  
>> dependency on javassist:javassist:3.4.GA and org.jboss.aop:jboss- 
>> aop:2.0.0.CR7 declaring a dependency on org.jboss:javassist: 
>> 3.6.0.GA, thus ending me up with (what Debian would call) an  
>> unstable configuration.
>> Depending on the wind, state of the moon, the weather in general  
>> Maven will put either on first on the class path. Which results in  
>> an unpredictable build.
>> My preference goes to javassist:javassist, because that reflects  
>> the package name and thus has less chance of name conflict.
>> maxb of Maven suggests the same:
>> (01:00:29 PM) wolfc: maxb_: I hope too that the first set of  
>> duplicates match central. As for the second set, it contains a lot  
>> of legacy and changing insights. So I was hoping to find something  
>> similar to 'obsoletes' in rpm or 'replaces' in dpkg. Or even a  
>> directive which forbids the use of javassist:javassist in the  
>> org.jboss:javassist pom.
>> (01:01:16 PM) maxb_: Well, I'd suggest going the other way, and  
>> using javassist:javassist, since that's the name that *has* made it  
>> into central
>> On the other hand org.jboss reflects our zone.
>> So before the week is done I want either artifact on the banned  
>> dependency list (which I'm now introducing in EJB3 build and I'll  
>> suggest to Dimitris to do the same for AS).
>> Note: I'm putting org.jboss.microcontainer:jboss-container on the  
>> ban right now, because I can almost spell out the getBeanInfo  
>> BeanAccess signature error in my dreams.
>> Carlo
>> _______________________________________________
>> 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