Re: [jboss-dev] jbossxb at 2.0.0-SNAPSHOT or 2.0.0.CR5
On Fri, 2008-03-14 at 14:11 +0200, Dimitris Andreadis wrote:
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.
My view is that the top-level should declare ALL dependencies unless
there is a good reason to delegate the choice to the subproject.
e.g. in this case, the jaxb choice should be delegated to JBossXB
since that is are xml parsing abstraction (same goes for Xerces etc.)
It certainly isn't upto JBossWS to choose the JAXB version for JBossAS.
It should be upto JBossWS to negotiate with JBossXB to get a release
with the version they want.
I have a thread about it here for the MC project
(see EXTERNAL TRANSITIVE DEPENDENCIES)
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131467
NOTE also the use of optional to stop unnecessary dependency
getting transferred into the dependent project.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx