[jboss-dev] jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5

[Dimitris Andreadis]

Adrian Brock wrote:
> I see a different issue (this is what I like about maven
> it always produces the same results for everybody :-)
> 
> It is caused by it using an early access runtime
> of JAXB 2.0
> 
>  javax.xml:jaxb-impl:jar:2.0EA3:compile
> 
> The old build used sun-jaxb:2.1.4
> 
> This is specified in the root pom.xml
> where did these versions come from, was it guesswork? :-)

For some reason that old version of the jaxb-impl library was explicity defined in root 
pom.xml, while in build-thirdparty.xml it was implicitly imported through jbossws.

Which brings the question:

Should the top-level project (in this case AS) declare the indirect dependency (e.g. 
jaxb-impl), or let the intermediate project bring it in, at whatever version it wants?

I guess the answer is, yes, if the top-level project wants to lock into a particular version.