Building a debug vs non-debug jar does sound like a good idea. -- 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. > > -- > Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
