You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> on 2003/10/28 03:57:53 UTC
Eclipse Plugin Mods
Mavens
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?
--
Alain Javier Guarnieri del Gesu (Javi) - javi@ajgdg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by Alain Javier Guarnieri del Gesu <ja...@ajgdg.com>.
* dion@multitask.com.au <di...@multitask.com.au> [2003-10-30 14:13]:
> Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> 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 - javi@ajgdg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by di...@multitask.com.au.
Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> 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.
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?
> 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.
> * 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.
> > 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.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by Alain Javier Guarnieri del Gesu <ja...@ajgdg.com>.
* dion@multitask.com.au <di...@multitask.com.au> [2003-10-29 14:26]:
> Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> wrote on 29/10/2003
> 09:04:35 PM:
>
> > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [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 - javi@ajgdg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by Alain Javier Guarnieri del Gesu <ja...@ajgdg.com>.
* Martin Skopp <sk...@riege.com> [2003-10-30 06:15]:
> On Wed, 2003-10-29 at 19:32, dion@multitask.com.au wrote:
> > > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [2003-10-28
> > 02:57]:
>>>> artifact-debug-1.0.jar
>>>> artifact-src-1.0.jar
>>>> artifact-doc-1.0.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.
> Isn't the "dist" plugin working fine and sufficient enought? The
> produced source zip files can easily assigned as sources-zips to a
> jar within eclipe.
The dist plugin creates a source jar where the source directory is
under a directory at artifact-1.0/src/java. Eclipse expects a souce
jar where the source directory is at the root of jar. That source
jar needs to be unjared for it to work with Eclipse.
> Ok, it would be perfect if the eclipse-plugin assignes the
> source-zip already, but I can live very good with the current way
> of doing it.
Have you done it? How? The Eclipse plugin is going to pulls from the
repository that are debug off for distribution. There is no way to
trace into that source. The trace is what I am trying to accomplish.
--
Alain Javier Guarnieri del Gesu (Javi) - javi@ajgdg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by Alain Javier Guarnieri del Gesu <ja...@ajgdg.com>.
* dion@multitask.com.au <di...@multitask.com.au> [2003-10-30 10:46]:
> Martin Skopp <sk...@riege.com> wrote on 30/10/2003 06:27:56 PM:
>
> > On Wed, 2003-10-29 at 19:32, dion@multitask.com.au wrote:
> > > > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [2003-10-28
>
> > > 02:57]:
> > > > > artifact-debug-1.0.jar
> > > > > artifact-src-1.0.jar
> > > > > artifact-doc-1.0.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.
> >
> > Isn't the "dist" plugin working fine and sufficient enought?
> No. It doesn't produce -debug or -doc jar/zips.
And the -src zip cannot be used with Eclipse.
--
Alain Javier Guarnieri del Gesu - javi@ajgdg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by di...@multitask.com.au.
Martin Skopp <sk...@riege.com> wrote on 30/10/2003 06:27:56 PM:
> On Wed, 2003-10-29 at 19:32, dion@multitask.com.au wrote:
> > > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [2003-10-28
> > 02:57]:
> > > > artifact-debug-1.0.jar
> > > > artifact-src-1.0.jar
> > > > artifact-doc-1.0.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.
>
> Isn't the "dist" plugin working fine and sufficient enought?
No. It doesn't produce -debug or -doc jar/zips.
> The produced source zip files can easily assigned as sources-zips to a
> jar within eclipe.
>
> Ok, it would be perfect if the eclipse-plugin assignes the source-zip
> already, but I can live very good with the current way of doing it.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by Martin Skopp <sk...@riege.com>.
On Wed, 2003-10-29 at 19:32, dion@multitask.com.au wrote:
> > * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [2003-10-28
> 02:57]:
> > > artifact-debug-1.0.jar
> > > artifact-src-1.0.jar
> > > artifact-doc-1.0.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.
Isn't the "dist" plugin working fine and sufficient enought?
The produced source zip files can easily assigned as sources-zips to a
jar within eclipe.
Ok, it would be perfect if the eclipse-plugin assignes the source-zip
already, but I can live very good with the current way of doing it.
--
Martin Skopp
Riege Software International GmbH
Support: mailto:maint@riege.com, Information: http://www.riege.com
This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4 5C0D 29E6 6A95 3D40 27B5
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by di...@multitask.com.au.
Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> wrote on 29/10/2003
09:04:35 PM:
> * Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [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.
But:
1) I'm not thrilled with the naming convention used.
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.
3) Please provide more detail on 'Maven does not do what I expected it to
do'. We can't help you if you don't tell us what is wrong.
4) You waited a whole day before being disillusioned? Not everyone will
have the same urgency as you.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Eclipse Plugin Mods
Posted by Alain Javier Guarnieri del Gesu <ja...@ajgdg.com>.
* Alain Javier Guarnieri del Gesu <ja...@ajgdg.com> [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.
--
Alain Javier Guarnieri del Gesu (Javi) - javi@ajgdg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org