You can by manipulating the transitive dependencies inherited through the poms. Just a quick word of warning: the process is a little mind bending, and is time consuming. That said, I'm sure the AppFuse community would love a leaner, meaner AppFuse deployment, so if you do decide to go ahead please do share your changes with us!
To see which dependencies are being included and where they are coming from, run mvn with the -X switch and pipe the output to a log file, e.g. mvn -X package > mvn.log. You can then scan through the inheritance tree to find out how certain jar files are finding their way into the war and insert appropriate <excludes> to the dependencies in the pom.xml file. I believe it has not been done on the project as a whole simply because there are no real issues for most users with a largish war file. Mike On 10/19/07, Micke <[EMAIL PROTECTED]> wrote: > > > Can I in a simple way shrink the size of the generated war? Is the minimum > size of a webapp based on appfuse ~20 MB? I'm pretty sure that I don't > need > all the included jar-files that is downloaded for me. > > Thanks, > Mike > -- > View this message in context: > http://www.nabble.com/Size-of-deployed-war-tf4653040s2369.html#a13294063 > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
