* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-11-02 16:19]: > Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote on 01/11/2003 > 07:36:34 AM: > > > * Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> [2003-10-31 > 17:59]: > > > In order to better support Eclipse, Maven should support the > > > creation of two targets for each project, a debug build and a > > > release build. These are to be provided as jars through the Maven > > > repository. It would require modifying the javac and dist plugins to > > > create the classes and jars respectivly. The release jars can be > > > used to distrubute the application, the debug jars can be used by > > > Eclipse or other IDEs to allow developers to trace exectution into > > > third-party libraries. > > > > I am volunteering, by the way. > > > > I'm having trouble hacking Xindice because of dependencies. Apache > > projects should all use the same endorsed jars. Maven and ibiblio > > may be a way to make that happen. > > > > I see it this way: > > > > * Create debug and release classes directories under target in the > > java plugin.
> I don't think the java plugin is the right one. > Maybe the jar plugin. > > * Create a directory in the repository called ide: > > - ide/artifact-1.0-dbg.jar > > - ide/artifact-1.0-src.jar > > - ide/artifact-1.0-doc.jar > I'd rather we kept the repository structure the same, and used jars/ or > distributions/. > > * Add an ide target to the dist plugin. > > I'd REALLY like to see this happen. If this is just not in the > > cards for Maven let me know so I can drop this. As it > > stands, I'm back to maintaining an ant script to pull and > > build debug versions of my dependencies. (There's no point > > in adding this to Maven without community adoption and > > ibiblio support.) > I'd really like this to happen, but I think we need to stick to > the existing structure in place and work out a good way of doing > this. If that means changing the dist plugin, so be it. > Comments? I'm suggesting hacking the java plugin because it seems that things would be simplier downstream if the java plugin made a distiction between debug and release builds. The java plugin could generate classes into debug or release subdirectories. target/java/classes/debug target/java/classes/release It would be a simple matter for the dist plugin to build jars using either the debug or release classes. Otherwise the dist plugin is going to have to wipe and rebuild the classes when the dist target, release or debug, is built to ensure that compiler switches are correct. Also, I'd like to see that both release and debug builds run through the full suite of unit tests. As far as the repository structure, jars or distirbutions is fine. What about the naming convention suggested for the files? -- Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
