[kepler-dev] Checking in duplicated jars

[Efrat Frank]

Hi Jagan,

I saw that you checked in several jars that already exist in the Kepler 
repository. This would significantly increase the size of a Kepler 
release while just one of the classes would actually be used depending 
on the classpath.

I think the best approach we should all take is to first try to use an 
existing jar. If a component requires an updated version, then we should 
check in the upgraded version with a version number.

Thanks,
Efrat