[jbosstools-dev] reusage of libraries

[Max Rydahl Andersen]

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

yes, but lets keep it short and sweet "deps", maybe? so dom4j could be org.jboss.tools.deps.dom4j ...?

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

Find the various versions and update to the latest used and run build to see what fails ;)

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

> dom4j is a given.

I don't know many others by heart..

/max

> - Rob
>
> Max Rydahl Andersen wrote:
>> On Fri, 11 Jan 2008 16:27:23 +0100, Koen Aers <koen.aers at jboss.com> 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
> 



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/