You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Boris Unckel <bo...@gmx.net> on 2006/09/13 19:43:54 UTC
[configuration] Surprising large dependency graph
Hello,
I just wanted to have a look at the structure and the design of commons
configuration. Most time I just
use eclipse, create a new project and download head from svn.
This time it was hard:
13 dependent libraries to get src and tests compile clean. I know I just
could use maven (currently just
maven 2 is installed) to solve this dependencies.
Is there anywhere a documentation (a picture) which compile time
dependencies are necessary for
commons projects? Is there any software architect who controls the
dependencies to avoid circular dependencies,
just allow a tree of dependencies and avoid a net of dependencies?
Regards
Boris
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [configuration] Surprising large dependency graph
Posted by Oliver Heger <ol...@oliver-heger.de>.
Boris Unckel wrote:
> Hello,
>
> I just wanted to have a look at the structure and the design of commons
> configuration. Most time I just
> use eclipse, create a new project and download head from svn.
>
> This time it was hard:
> 13 dependent libraries to get src and tests compile clean. I know I just
> could use maven (currently just
> maven 2 is installed) to solve this dependencies.
>
> Is there anywhere a documentation (a picture) which compile time
> dependencies are necessary for
> commons projects? Is there any software architect who controls the
> dependencies to avoid circular dependencies,
> just allow a tree of dependencies and avoid a net of dependencies?
>
> Regards
> Boris
>
Yes, Configuration needs a bunch of dependencies. Interestingly most of
them are needed for testing, e.g. mock objects, JNDI, hsqldb. Some of
the dependencies like xerces or xalan are only needed for JDK 1.3. On
our dependencies page [1] we list, which runtime dependencies are need
for which specific feature.
I am not aware of any supervising instance, which has an eye on the
dependencies of commons components. On general@ there is currently a
thread about this topic however.
Oliver
[1] http://jakarta.apache.org/commons/configuration/dependencies.html
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org