Zhang, Larry (L.) wrote:

When using Struts, it is easy to download struts.jar and put it in your class path and then you are done. What if you want to use source code instead of binary download. How can we identify those classes included in struts.jar from the source download? This seems not to be easy since source download bundle seems to be very messy.



The best way to understand what goes in to struts.jar is to examine the top-level build.xml file in the source distribution ... in particular the "compile.library" target that creates it. You'll find that it combines:

* Compiled Java classes from "src/share".

* Resource files (properties) from "src/share".

* Tag library definition (TLD) files generated from "doc/userGuide/struts-*.xml"
in the META-INF directory.


* META-INF/MANIFEST.MF based on one in "conf/share".

This has basically been the model from the beginning up to the recent nightly builds of 1.2. We're looking at ways to simplifying the source architecture (and build system) as part of moving Struts to being a top level Apache project, but no concrete work has happend yet.

Thanks.

Larry Zhang
Ford Motor Company



Craig


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to