http://blog.artifact-software.com/tech/?p=121 describes how we
approached the problem of reducing the number of jars on the classpath
while simplifying the development process and speeding up builds.
It is a bit different from what you are trying to do tactically but I
think that it may address your ultimate problem from a strategic point
of view.
Ron
On 10/03/2015 10:33 AM, D C wrote:
I was going to tag this onto my previous post, but I figured the issue is
unique enough to be a different topic.
When I run dependency:tree (with an empty .m2), I get a nice tree graph
showing 49 items. I would expect then my .m2/repository to have 49 items
in it. In actuality, my .m2 now has 251 artifacts.
I want to collect only the artifacts that my application needs to run.
Would I be safe if I just package up the 49 items listed in the dependency
tree output?
This would also be useful to reduce because I create my class path like so:
$ find ~/.m2/repository/ -name "*.jar" | xargs | sed 's/ /;/g'
The more I can remove from there, the better.
Thanks,
Dan
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
