On Mon, Apr 2, 2012 at 6:29 PM, Chris Hostetter <[email protected]> wrote: > > : I've just modified ivy.xml to use jackson 1.7.4 and this triggered an > : interesting situation in which I ended up having two versions of > : jackson in my checkout. This begs the question of what should we be > : doing to remove stale JARs on an update of ivy descriptors. Should > : "ant clean" remove all the JARs? > > rmuir added "clean-jars" ... but i was kind of wondering hte same thing. > > prior to ivy, an "svn up && ant clean" would get you into a good state > because the svn up would remove the old jars ... seems like we should just > make clean call clean-jars (if they *haven't* changed they'll still be in > your ivy cache) >
This is way too much effort for what you will get. effort better spent removing lib/ and 'copies of jars' totally and instead having ivy just put this in the classpath. The reason it is the way it is: is to not break packaging etc tasks. IFF someone wants to open an issue and clean all this up and fix and test all of the packaging logic, thats fine for trunk. but its not ok for the branch. -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
