From: <Joe...@El...> - 2004-12-02 18:35:49
|
Hi Alex, Alex Karasulu wrote on Thursday, December 02, 2004 5:59 PM: > Hiya, >=20 > I just started using Javaapp pluging and it works well. Thanks btw! You're welcome. > I'm using it to create a single executable jar for Eve the Apache > Directory project's main server. I notice there's lot of > apache peeps > on the project (hey!). The only problem is that the final > bundle is 2.7 > Mb in size. I was wondering if I can filter out the classes that I > don't need in the dependencies using some kind of switch or property. Well, currently you can only filter out the dependency itself. This = helps if you have test dependencies or the user must provide runtime = dependencies himself (e.g. client jars for an app server ... you cannot = know what he uses). > I'm thinking this might not be in place and if not I don't > mind adding > it. Anyone think about this feature before? Any ideas regarding how > this can be done to determine all dependencies even ones that get > dynamically loaded?=20 So your thinking of a fine-grained exclusion i.e. the unsused classes. = Well, yes this is something I thought about too, but not necessarily = only for javaapp, but also for an obfuscator like yguard. But no further = thought yet. - J=F6rg |