"Eric Pugh" <[EMAIL PROTECTED]> writes:
>As far as the jar thing goes there are advantages and disadvantages.
>One big jar is easier to deal with.
>Lots of little jars allow you to include ONLY what you want.
>Lots of little jars are easier to update one segment.
Lots of little jars lead to things like this:
% ls commons-httpclient/jars/*.jar
commons-httpclient/jars/commons-httpclient-2.0-alpha3.jar
commons-httpclient/jars/commons-httpclient-2.0-beta1.jar
commons-httpclient/jars/commons-httpclient-2.0-rc1.jar
commons-httpclient/jars/commons-httpclient-2.0alpha1-20020829.jar
Maven dependencies on c-httpclient from the maven build. One would
think that the "home of the reactor" would be able to get a single,
unified set of dependencies.
I personally prefer the "a few big jars" approach. But it's just an opinion,
feel free to work on Fulcrum as you like.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
