If the instructions on amending the build process were available, they might also be submitted to Gump, which builds a ton of JARs every day.
http://gump.covalent.net/jars/latest/ The driving force behind Gump is Sam Ruby, who I've copied into this reply. If for some reason the process cannot be automated at this time, perhaps you should setup a SourceForge project where these JARs can be pooled and shared. -Ted. 12/23/2002 2:18:52 PM, David Morris <[EMAIL PROTECTED]> wrote: >I came upon this message while looking for Eclipse >IDE information. To make Struts easier to use in Eclipse, I >import the jar version followed by the java source and re-export >them into a bin/source jar. This corrects line feed issues and >makes it easy to step from my code to struts code in the >debugger. I do this for Struts and Tomcat as well as some of >the commons components. It takes about 20 minutes or so >for each jar file but makes it easy to find problems related >to things like naming errors. I end up doing this for every >new major release of Struts or Tomcat. > >It would be nice if there was a repository of pre-build jars >that a person could download with source included. I don't >know how easy it would be to build these as part of your >build process because of the line feed issues but I know that >other Windows eclipse uses who I have shared these jar files >seemed to appreciate the effort. > >David Morris -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
