I suggest a new module "dependencies", within which each dependency has its own wrapper plugin.

How should we go about deciding which versions we're all going to start using?

Also which dependencies are common enough that we should standardize on?

dom4j is a given.

- Rob Max Rydahl Andersen wrote: > On Fri, 11 Jan 2008 16:27:23 +0100, Koen Aers <koen.aers(a)jboss.com&gt; wrote: > > >>> 1) put them in a org.jboss.tools prefixed plugin (e.g. org.jboss.tools.org.dom4j) and >>> share that. >>> >> I am in favour of doing this actually. But I started to work my way >> around the dom4j dependency by using JAXP. Yes I know, JAXP is a PITA >> but if it makes this nasty dependency go away that is an advantage. >> > > JAXP ? sounds crazy ;) > > In any case it won't go away from jbosstools as long as hibernate is using dom4j... > > >>> 2) keep doing what we do now which is simple. >>> >> It is simple, but you end up with an unmanageable hidden dependency >> tree. I use dom4j version 1.4, you use 1.6 and still another guy uses >> 1.6.1. Not that much of a problem, but it is not very clean. >> > > gawd - I completely ignored that one..it must be the vacation. > > Yes - that is something that makes it sensible to change them to "proper" plugins. > > /max > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >