You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Javier del Gesu <de...@thinknola.com> on 2003/10/24 22:12:44 UTC
Debug Version of Dependencies
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.
--
Javier del Gesu - delgesu@thinknola.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Debug Version of Dependencies
Posted by di...@multitask.com.au.
Source jars can easily be placed in the repository.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Javier del Gesu <de...@thinknola.com> wrote on 25/10/2003 09:34:59
AM:
> * Javier del Gesu <de...@thinknola.com> [2003-10-24 21:03]:
> > * Javier del Gesu <de...@thinknola.com> [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?
>
> Uh? Help?
>
> --
> Javier del Gesu - delgesu@thinknola.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Debug Version of Dependencies
Posted by Javier del Gesu <de...@thinknola.com>.
* Javier del Gesu <de...@thinknola.com> [2003-10-24 21:03]:
> * Javier del Gesu <de...@thinknola.com> [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?
Uh? Help?
--
Javier del Gesu - delgesu@thinknola.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Debug Version of Dependencies
Posted by Javier del Gesu <de...@thinknola.com>.
* Javier del Gesu <de...@thinknola.com> [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 - delgesu@thinknola.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org