* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-10-29 14:26]:
> Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote on 29/10/2003
> 09:04:35 PM:
>
> > * Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> [2003-10-28
> 02:57]:
> > > I've created an ant script that pulls and builds about a dozen
> > > dependencies for my project. Output goes to the local maven
> > > repository. For each artifact, I create three files:
> > >
> > > artifact-debug-1.0.jar
> > > artifact-src-1.0.jar
> > > artifact-doc-1.0.jar
> > >
> > > Now I'd like to hack the Eclipse plugin to detect the presence of
> > > these these jars and use them in the .classpath. That is, I want to
> > > have the eclipse plugin create classpath entries with the debug
> > > version of the libraries set. The source and documentation jars will
> > > also be set appropirately.
> > >
> > > Sound like a good idea? Is there a better way?
> > I adoped Maven in order to coordiate my Eclipse and CLI build
> > environments. I'm finding that Maven does not do what I expected it
> > to do. I'm working around Maven. I'd work with it, if there was any
> > interest in distributing source and debug jars.
> There is interest in distributing source and debug jars.
It is something that I would look into doing with Maven, if it would
be of use to Maven.
> 1) I'm not thrilled with the naming convention used.
I'd start by positing that there ought to be two outputs from a
build of a project, debug and release. I'm don't feel that there
should be more that these two outputs. It is not necessary to make
build targets any more configurable. Debug has debugging on and
optimize off, release is the vice-versa.
The naming convention could be based on:
* A perversion of the names, as above.
* Modification of the repository structure.
dbg/artifact-1.0.jar
rel/artifact-1.0.jar
src/artifact-1.0.jar
doc/artifact-1.0.jar
* Both.
Which direction would you take?
> 2) There is nothing in maven to create these artifacts yet. This should be
> done as well, otherwise the work on the eclipse plugin is of
> very limited usefulness.
I suppose this means working with the javac goals.
--
Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]