* 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.
* 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
* Add an ide target to the dist plugin.
Then I'd be able to suppy builds for xindice, xerces, xalan, cocoon,
junit, xmlunit, XMLWriter, and more.
A natural extension of this would be a patch plugin that would
generate patches to changes made to the dependency. These
could be made available to the projects in question.
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.)
--
Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
