* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-10-30 14:13]:
> Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> wrote on 30/10/2003 
> 02:47:50 AM:
> 
> > > 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 jars by default are built with debug on. so artifact-1.0.jar is a 
> debug jar. 

> What's the distinction here between debug and release jars? Eclipse itself 
> doesn't have a 'debug' jar vs non-debug jar distinction. The dist plugin 
> could easily be called with debug off if that's what you want.

This is new to me. So, the distributions from ibibilio.com have
debug symbols and are not optimized? If so, it seems that there
ought to be a non-debug optimized jar available.

> I'd really like to see a way of attaching javadoc to jars for eclipse, but 
> eclipse itself wants a URL or file, not a jar or zip file. I'm not sure if 
> a jar: URL would work. Have you tried it?

It works in Eclipse 3.0, a jar url that can point to a directory
within the jar. (But now I, can't seem to find where the documetation
url is stored in Eclipse, it is not in .classpath.)

> > 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
> 
> I'd rather not change the repository structure.

Understood. Also, it would make sense to keep the information
pertaining to the jar contents in the jar name.

> > * Both.
> > 
> > Which direction would you take?
> 
> At the moment, I'm trying to see how we can fit in with Eclipse, and don't 
> see an easy way to do this other than making a special source jar.

Other than changing Eclipse to index into the source directory of a
distribution, I can't see it either. Even then, you would have to
have the POM of the dependency to know where the source directory is
within the distribution jar.

> > > 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.

> Or adapting the dist or jar plugins to create the source jar.

Yes. Now I see that dist and jar create the jars. But I imagined
that javac might have to be modified to build debug and release
versions of the classes. (It still makes sense to me, at least for
the difference between optimize on and off.)

-- 
Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to