Dennis Sosnoski wrote: > While we're looking into this, we should also check the war file > contents. It looks like the full set of jars are included, which is > certainly unnecessary. JiBX support only needs axis2-jibx-XXX.jar and > jibx-run-XXX.jar, not the much larger bcel-XXX.jar (.5 MB) and > jibx-bind-XXX.jar (.3 MB). I can strip these two unnecessary files out > of the war build if someone wants to point me at the appropriate magic > maven file, but I'm sure there's a lot more that can also be eliminated. >
Done. Removed bcel-XXX.jar and jibx-bind-XXX.jar from the build. BTW, we have no way of knowing which jars are really required. What the maven scripts does is (in case if some one doesn't know), when we name some modules, it will pick up all the dependencies of those modules and add them to the war (refer cache-war-deps goal in maven.xml). How I overcome the above problem is deleting un-necessary files, after the above goal is invoked (see line 384 of maven.xml). I could have done the same thing by excluding the jars within the war ant task, but I opted the above. Those couple of lines were to reveal the magic behind maven logic :). -- Chinthaka
signature.asc
Description: OpenPGP digital signature
