General question regarding dependencies

[Alex Karasulu <ao...@bellsouth.net>]

Hi,

Guys I have a single class that a (maven) project depends on in commons-lang.  Generally I use commons-lang all over the place and think its great.  But what do I do if I only depend on ValuedEnum to have type safe enumerations?

Should I just copy the class like many commons projects do (referring to the what digester did with a particular collections class from commons-collections)?  Or should I just keep the dependency?  I don't mind the dependency especially when where i use this project's artifact usually includes commons-lang.

Alex

Re: General question regarding dependencies

[Niclas Hedhman <ni...@hedhman.org>]

From: "Alex Karasulu" <ao...@bellsouth.net>

> Guys I have a single class that a (maven) project depends on in
commons-lang.  Generally I use commons-lang all over the place and think its
great.  But what do I do if I only depend on ValuedEnum to have type safe
enumerations?
>
> Should I just copy the class like many commons projects do (referring to
the what digester did with a particular collections class from
commons-collections)?  Or should I just keep the dependency?  I don't mind
the dependency especially when where i use this project's artifact usually
includes commons-lang.

I would vote for the "keep the full dependency" option. Otherwise we are
risking some nasty surprises down the road when other classes are depended
upon as well.

Niclas

RE: General question regarding dependencies

[Stephen McConnell <mc...@apache.org>]

> -----Original Message-----
> From: Alex Karasulu [mailto:aok123@bellsouth.net]
> Sent: 05 September 2004 06:40
> To: directory-dev@incubator.apache.org
> Subject: General question regarding dependencies
> 
> Hi,
> 
> Guys I have a single class that a (maven) project depends on in
commons-
> lang.  Generally I use commons-lang all over the place and think its
> great.  But what do I do if I only depend on ValuedEnum to have type
safe
> enumerations?
> 
> Should I just copy the class like many commons projects do (referring
to
> the what digester did with a particular collections class from
commons-
> collections)?  Or should I just keep the dependency?  I don't mind the
> dependency especially when where i use this project's artifact usually
> includes commons-lang.

IMO - If the class is used in a bootstrap scenario (i.e. you want to
keep thing a small as possible and minimize deps - then copy the class
(under a directory package name).  Otherwise maintain the dependency
reference.  

Steve.


> Alex