* Eric Pugh <[EMAIL PROTECTED]> [2003-11-11 11:49]: > > -- > > dIon Gillard, Multitask Consulting > > Blog: http://blogs.codehaus.org/people/dion/ > > Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc > > > > > > Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote > > on 10/11/2003 > > 03:38:49 AM: > > > > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-11-09 06:50]: > > > > Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote on > > 09/11/2003 > > > > 12:45:46 PM: > > > > > > > > > * Vikas Phonsa <[EMAIL PROTECTED]> [2003-11-07 21:19]: > > > > > > Can I have the jar goal generate a jar that includes > > the source > > code > > > > file > > > > > > also beside the .class files. > > > > > > > > > > I've been asking about creating separate debug and release build > > > > > targets for some time now. A debug target would have a > > source jar. > > > > > This would make is easy to deploy the artifacts for use with > > > > > Eclipse. > > > > > > > where did we get with this? > > > > > > > > Last I remember, my suggest was to use the dist plugin, > > not the jar > > > > plugin. > > > > > > I will start working on it this week. It just seems to me that Maven > > > ought to support the two inevitable output paths, debug and release, > > > but after reading through java, jar, and dist, I'll be able to > > > better comment. > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 10, 2003 12:43 AM > > To: Maven Users List > > Subject: Re: including source in jar > > > > > > Building a debug vs non-debug jar does sound like a good idea.
> I like the idea of including src etc in the jar.. However, we > should also think about how to work with non Maven jars.. Is > there any sense to to adding something to the Eclipse plugin that > allows you to define where to get src from? > > For instance, I keep the source for OSWorkflow, and Ant built > project, on c:\java\oswf\src\java.. So, would it make sense to > have an .xml file that maps the groupId/artifactID to a location? > > <srcArtifact> > <groupId>opensymphony</groupId> > <artifactId>osworkflow-2.6-dev</artifactId> > <location>c:\java\oswf\src\java</location> > <srcArtifact> > > This would at least obviate the need to change a whole bunch of > things... Of course, every user is maintaining their own > source... Every user maintaining their own source is what I am trying to elminiate with this. It should be possible to pull down a jar of debug classes and a jar of source files so that someone is able to trace into their project dependencies. If this is standardized, these debug and source jars can be kept on ibiblio. Creating a source jar is not difficult. Users can just create a jar using their favorite zip utility and put it in their local repository. Or else, they can do as I have, and create ant scripts to pull source from project repositories and build the debug and source jars. But keep taking about this, I'd love to get a dialog going. -- Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
