Why apache commons are bundled along with click

[balachandra maddina <ch...@gmail.com>]

Hi There,

   Im wondering why the apache commons classes are bundled along with
click. what would be the case if use click jar file and apache commons
jar files in my webapp? would that cause any issues?

any help would be appreciated

Thank you,
bala.

Re: Why apache commons are bundled along with click

["Adrian A." <a....@gmail.com>]

>    Im wondering why the apache commons classes are bundled along with
> click. 
If you look in the Click distribution (or build Click yourself), you 
will see the following two packages too:
1. click-${version}.jar
and
2. click-nodeps-${version}.jar

The first one contains all the required dependencies (so Apache commons 
too) so that a Click based web application can run on the spot without 
extra effort from the user.
The second one, as it's names suggests: xxx-nodeps-xxx.jar contains no 
dependencies, so you will need to supply them in order to run the 
application correctly.

 > what would be the case if use click jar file and apache commons
 > jar files in my webapp? would that cause any issues?
IMHO it is not recommended to duplicate the classes (they might have 
different versions too).

You can find here the JARs Click relies on:
http://incubator.apache.org/click/docs/developer-guide/building.html#framework-dependencies
(if you want to supply them manually)

Adrian.