On Jan 3, 2008, at 2:16 PM, Ted Kosan wrote: > Robert wrote: > >> Here is the reduced list of .jar files I was able >>> to achieve a successful build with: >>> >>> Acme.jar commons-cli-1.0.jar netscape.jar >>> ant-contrib.jar itext-1.4.5.jar vecmath1.2-1.14.jar >> >> Excellent. Have you been able to build any of these? Perhaps we >> should have a "dependencies" directory at the top level of the spkg >> where we build all these, then copy the jars to the right place. > > The idea of a dependences directory sounds good. I have not tried > building the support jars from source yet, but if you would like me to > I can work on this.
That would be great. >> I think we can save also on build time by not building documentation >> and signed jars. > > Not building the documentation is easy to do because the code resides > in its own target. However, the jar signing code is inside the same > target that builds the jmol jars so it would require modifying the > jmol build.xml file to bypass the jar signing. > > So, is it better to just let it sign the jar or to edit the jmol > build.xml file so it bypasses the signing code? Given that it probably doesn't take too much time, and you already figured out how to do it smootly, I don't think it's worth it to make a custom build.xml file. - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
