* Javier del Gesu <[EMAIL PROTECTED]> [2003-10-24 20:12]: > I want to be able to trace into Xerces/Xalan/Xindice/Cocoon/Avalon > when debugging my application. It doesn't seem that the dependencies > downloaded from ibiblio will permit this, I don't see any source > files. Is there a standard strategy for building debug dependencies > and setting a debug classpath? > > I might add that I've created build scripts for all of the above > save Avalon in ant that pull the projects, patch them if necessary, > and build them. This is important to me, so I'm liable to contribute > on this matter.
Acutally, I created an XSLT transform. The transform generates an ant file that pulls and builds about a dozen dependencies. I can then point to them in Eclipse and trace into them. The ant macro document that I feed the transform has a place to specify a source respository, patch actions (necssary for little OS X incompatabilites), and build instructions. I'm looking around. Gump looks to big, and I often want to pull a specific branch. First guess: Use the existing Ant script to build the files to my local repository. Better still: Wouldn't it be nice if there were debug jars and source zips on ibiblio? Did I miss something? -- Javier del Gesu - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
