You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Stephane Nicoll <st...@gmail.com> on 2006/01/02 14:13:20 UTC
Re: [m1] Support of Java source artifact planned?
Hey,
It seems that the standard place to delpoy Java soures is in the
java-sources directory on the repository. The pattern should be
something like {artifactId}-{version}-source.jar ; Check the eclipse
plugin (1.10) for more details.
I think we should first define a standard location and then create a
maven one artifact handler for Java source code.
Thanks,
Stéphane
On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> Hello Stephane,
> I have the install and deploy goals implemented as well. it would be nice to
> have the location somehow standardized, so that the sources don't appear at
> many different places in the remote repository. I've been using the "src.jar"
> location (made according to the "javadoc.jar" location) in the
> maven-mevenide-plugin and the netbeans IDE integration so far. Unfortunately
> there's not much sources in the remote repository just yet (neither is
> javadocs :( ). I try uploading the sources for the mevenide project when I
> do a release.
> http://www.ibiblio.org/maven/mevenide/src.jars/
>
> regarding tools to download, I don't know about maven goals, but I can
> download it from Netbeans (user can check the remote repositories for
> javadocs and sources and mevenide will download it for him/her)
>
> Milos
>
> On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> >
> > Hi Milos,
> >
> > I do have such a goal already as well. What I mean is a support of the
> > artifact plugin for the java.src type. I want to be sure that it would
> > deploy in the java-sources directory of the repository (so that this
> > could be found by the eclipse plugin).
> >
> > Similarly, I would like to know if they are tools to *download* such
> > artifact from the repository if they are not found in the local
> > repository (for now the patch of MPECLIPSE-60 is quite a workaround).
> >
> > Cheers,
> > Stéphane
> >
> > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > not sure it's exactly what you are looking for but about a year ago I
> > create
> > > a bunch of goals to deal with creating source distributions, installing
> > and
> > > deploying them. I think I filed it as an enhancement for the dist plugin
> > but
> > > it's there since then untouched ;(
> > > in the mean time i've added it to the maven-mevenide-plugin (a plugin
> > that
> > > I ship together with the mevenide-netbeans. it has many, quite
> > unrelated
> > > goals that are useful for the IDE integration.
> > > http://mevenide.codehaus.org/maven-mevenide-plugin/changes-report.htmlhas
> > > more details or check the sources at
> > > http://cvs.mevenide.codehaus.org/maven-plugins/maven-mevenide-plugin/
> > >
> > > Regards
> > >
> > > Milos
> > >
> > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > >
> > > > anyone?
> > > >
> > > > On 12/28/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > Hi,
> > > > >
> > > > > Our production is currently running m1.0.2 and I am planning to move
> > > > > to 1.1 as soon as possible (is there a release date for 1.1 by the
> > > > > way?).
> > > > >
> > > > > We have used for a long time eclipse plugin 1.9 patched with
> > > > > MPECLIPSE-60 (which basically download java sources from the
> > > > > repository).
> > > > >
> > > > > Eclipse plugin 1.10 supports two locations for thoses sources: the
> > src
> > > > > directory and the new java-sources directory which is the one used
> > > > > with m2.
> > > > >
> > > > > Having java-sources as an artifact is really needed here because
> > > > > Eclipse plugin 1.10 is simply unable to download the java-sources
> > from
> > > > > the repository. The current patch localted in MECLIPSE-60 is unable
> > to
> > > > > refresh snapshots from the repository. We do have scripts to do such
> > > > > things for jars/wars and the like. Any plan to add the support of
> > java
> > > > > sources?
> > > > >
> > > > > If anyone can point me to the right direction, I am willing to
> > > > > implement this myself.
> > > > >
> > > > > Cheers,
> > > > > Stéphane
> > > > >
> > > > > --
> > > > > .::You're welcome ::.
> > > > >
> > > >
> > > >
> > > > --
> > > > .::You're welcome ::.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > .::You're welcome ::.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] Support of Java source artifact planned?
Posted by Arnaud HERITIER <ah...@gmail.com>.
I think it was done like this to use the artifact taglib (which by default
deploys the artifact in <groupId>/<type>/<artifactid>-<version>.<type>).
It could be possible to change it with a custom ArtifactTypeHandler (as done
in the ejb plugin for example) but nobody asked me to do it. I'm not sure
that this goal is often used.
Arnaud
On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
>
> what would be the full path in the remote repository then?
> mevenide/java-sources/mevenide-core-0.10-source.jar ?
>
> that doesn't conform to the <groupId>/<type>/<artifactid>-<version>.<type>
> pattern that the repository has otherwise.
> I think javadoc plugin had
> mevenide/javadocs/mevenide-core-0.10-javadoc.jarin some older version
> of the maven-javadoc-plugin but lately it has been
> changed to mevenide/javadoc.jars/mevenide-core-0.10.javadoc.jar
> I wonder what was the reason for the change? Maybe a javadoc-plugin
> developer could shed some light on that?
>
>
> Regards
>
> Milos
>
> On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
> >
> > Hey,
> >
> > It seems that the standard place to delpoy Java soures is in the
> > java-sources directory on the repository. The pattern should be
> > something like {artifactId}-{version}-source.jar ; Check the eclipse
> > plugin (1.10) for more details.
> >
> > I think we should first define a standard location and then create a
> > maven one artifact handler for Java source code.
> >
> > Thanks,
> > Stéphane
> >
> > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > Hello Stephane,
> > > I have the install and deploy goals implemented as well. it would be
> > nice to
> > > have the location somehow standardized, so that the sources don't
> appear
> > at
> > > many different places in the remote repository. I've been using the "
> > src.jar"
> > > location (made according to the "javadoc.jar" location) in the
> > > maven-mevenide-plugin and the netbeans IDE integration so far.
> > Unfortunately
> > > there's not much sources in the remote repository just yet (neither is
> > > javadocs :( ). I try uploading the sources for the mevenide project
> when
> > I
> > > do a release.
> > > http://www.ibiblio.org/maven/mevenide/src.jars/
> > >
> > > regarding tools to download, I don't know about maven goals, but I can
> > > download it from Netbeans (user can check the remote repositories for
> > > javadocs and sources and mevenide will download it for him/her)
> > >
> > > Milos
> > >
> > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > >
> > > > Hi Milos,
> > > >
> > > > I do have such a goal already as well. What I mean is a support of
> the
> > > > artifact plugin for the java.src type. I want to be sure that it
> would
> > > > deploy in the java-sources directory of the repository (so that this
> > > > could be found by the eclipse plugin).
> > > >
> > > > Similarly, I would like to know if they are tools to *download* such
> > > > artifact from the repository if they are not found in the local
> > > > repository (for now the patch of MPECLIPSE-60 is quite a
> workaround).
> > > >
> > > > Cheers,
> > > > Stéphane
> > > >
> > > > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > > > not sure it's exactly what you are looking for but about a year
> ago
> > I
> > > > create
> > > > > a bunch of goals to deal with creating source distributions,
> > installing
> > > > and
> > > > > deploying them. I think I filed it as an enhancement for the dist
> > plugin
> > > > but
> > > > > it's there since then untouched ;(
> > > > > in the mean time i've added it to the maven-mevenide-plugin
> > (a plugin
> > > > that
> > > > > I ship together with the mevenide-netbeans. it has many, quite
> > > > unrelated
> > > > > goals that are useful for the IDE integration.
> > > > >
> >
> http://mevenide.codehaus.org/maven-mevenide-plugin/changes-report.htmlhas
> > > > > more details or check the sources at
> > > > >
> > http://cvs.mevenide.codehaus.org/maven-plugins/maven-mevenide-plugin/
> > > > >
> > > > > Regards
> > > > >
> > > > > Milos
> > > > >
> > > > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > >
> > > > > > anyone?
> > > > > >
> > > > > > On 12/28/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > Our production is currently running m1.0.2 and I am planning
> to
> > move
> > > > > > > to 1.1 as soon as possible (is there a release date for 1.1 by
> > the
> > > > > > > way?).
> > > > > > >
> > > > > > > We have used for a long time eclipse plugin 1.9 patched with
> > > > > > > MPECLIPSE-60 (which basically download java sources from the
> > > > > > > repository).
> > > > > > >
> > > > > > > Eclipse plugin 1.10 supports two locations for thoses sources:
> > the
> > > > src
> > > > > > > directory and the new java-sources directory which is the one
> > used
> > > > > > > with m2.
> > > > > > >
> > > > > > > Having java-sources as an artifact is really needed here
> because
> > > > > > > Eclipse plugin 1.10 is simply unable to download the
> > java-sources
> > > > from
> > > > > > > the repository. The current patch localted in MECLIPSE-60 is
> > unable
> > > > to
> > > > > > > refresh snapshots from the repository. We do have scripts to
> do
> > such
> > > > > > > things for jars/wars and the like. Any plan to add the support
> > of
> > > > java
> > > > > > > sources?
> > > > > > >
> > > > > > > If anyone can point me to the right direction, I am willing to
> > > > > > > implement this myself.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Stéphane
> > > > > > >
> > > > > > > --
> > > > > > > .::You're welcome ::.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > .::You're welcome ::.
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > .::You're welcome ::.
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > .::You're welcome ::.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
Re: [m1] Support of Java source artifact planned?
Posted by Stephane Nicoll <st...@gmail.com>.
That would be good!
Thanks,
Stéphane
On 1/2/06, Arnaud HERITIER <ah...@gmail.com> wrote:
> It's quite easy to create a custom artifact handler [1] to deploy sources on
> the repository with a compatible layout for m2.
> But where will we add it ? We don't have a plugin which deploy sources
> actually. We have the distribution plugin but it deploys all the project.
> Where could we add it ?
> I can create a new plugin if necessary. A maven-sources-plugin for m1.
>
> Arnaud
>
>
> [1]
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/ejb/src/main/org/apache/maven/ejb/EJBArtifactTypeHandler.java?rev=232640&view=markup
>
>
> On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
> >
> > On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> > > since you do the work, you pick. :)
> > > Just let me know then, I'll update the mevenide support then.
> >
> > Issue created: http://jira.codehaus.org/browse/MAVEN-1736
> >
> > Regards,
> > Stéphane
> >
> > --
> > .::You're welcome ::.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] Support of Java source artifact planned?
Posted by Arnaud HERITIER <ah...@gmail.com>.
It's quite easy to create a custom artifact handler [1] to deploy sources on
the repository with a compatible layout for m2.
But where will we add it ? We don't have a plugin which deploy sources
actually. We have the distribution plugin but it deploys all the project.
Where could we add it ?
I can create a new plugin if necessary. A maven-sources-plugin for m1.
Arnaud
[1]
http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/ejb/src/main/org/apache/maven/ejb/EJBArtifactTypeHandler.java?rev=232640&view=markup
On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
>
> On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> > since you do the work, you pick. :)
> > Just let me know then, I'll update the mevenide support then.
>
> Issue created: http://jira.codehaus.org/browse/MAVEN-1736
>
> Regards,
> Stéphane
>
> --
> .::You're welcome ::.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [m1] Support of Java source artifact planned?
Posted by Stephane Nicoll <st...@gmail.com>.
On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> since you do the work, you pick. :)
> Just let me know then, I'll update the mevenide support then.
Issue created: http://jira.codehaus.org/browse/MAVEN-1736
Regards,
Stéphane
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] Support of Java source artifact planned?
Posted by Milos Kleint <mk...@gmail.com>.
On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
>
> On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> > Ok, now with M2 in the picture it seems to make some sense. However
> it's
> > unfortunate that we won't be able to use the artifact taglib for
> uploading
> > the artifacts. (if I understood Arnaud correctly in his reply)
>
> We just need to implement an custom artifact type handler. Arnaud, can
> you help me on that?
>
> > I don't care which of the formats becomes standard, in the IDE I'll be
> > checking the standard and old location transparently to te user.
> Hopefully
> > we get some more source jars in the remote repository..
>
> I don't care either, we just need a standardization for this before 1.1final.
since you do the work, you pick. :)
Just let me know then, I'll update the mevenide support then.
Regards
Milos
Cheers,
> Stéphane
>
>
> .::You're welcome ::.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [m1] Support of Java source artifact planned?
Posted by Stephane Nicoll <st...@gmail.com>.
On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> Ok, now with M2 in the picture it seems to make some sense. However it's
> unfortunate that we won't be able to use the artifact taglib for uploading
> the artifacts. (if I understood Arnaud correctly in his reply)
We just need to implement an custom artifact type handler. Arnaud, can
you help me on that?
> I don't care which of the formats becomes standard, in the IDE I'll be
> checking the standard and old location transparently to te user. Hopefully
> we get some more source jars in the remote repository..
I don't care either, we just need a standardization for this before 1.1 final.
Cheers,
Stéphane
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] Support of Java source artifact planned?
Posted by Milos Kleint <mk...@gmail.com>.
On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
>
> Milos,
>
> Not a single clue about it. The only reason I see is explained in the
> eclipse plugin changes:
>
> <snip>
> Java source location now defaults to
> MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar
> (standard location where source artifacts are deployed by the m2
> source plugin in a legacy/m1 repository layout). The path
> ${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension}
> is still supported for backward compatibility and it will be used
> only if a file already exists at that location. Thanks to Fabrizio
> Giustina.
> <snip>
>
> It seems this is the standard location used by the m2 source plugin. I
> don't care about the final location actually: we need to standardize
> this asap (at least before 1.1 final I would say). Keeping
> compatibility with M2 seems important to me as well.
Ok, now with M2 in the picture it seems to make some sense. However it's
unfortunate that we won't be able to use the artifact taglib for uploading
the artifacts. (if I understood Arnaud correctly in his reply)
I don't care which of the formats becomes standard, in the IDE I'll be
checking the standard and old location transparently to te user. Hopefully
we get some more source jars in the remote repository..
Milos
Regards,
> Stéphane
>
>
> On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> > what would be the full path in the remote repository then?
> > mevenide/java-sources/mevenide-core-0.10-source.jar ?
> >
> > that doesn't conform to the
> <groupId>/<type>/<artifactid>-<version>.<type>
> > pattern that the repository has otherwise.
> > I think javadoc plugin had
> > mevenide/javadocs/mevenide-core-0.10-javadoc.jarin some older version
> > of the maven-javadoc-plugin but lately it has been
> > changed to mevenide/javadoc.jars/mevenide-core-0.10.javadoc.jar
> > I wonder what was the reason for the change? Maybe a javadoc-plugin
> > developer could shed some light on that?
> >
> >
> > Regards
> >
> > Milos
> >
> > On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
> > >
> > > Hey,
> > >
> > > It seems that the standard place to delpoy Java soures is in the
> > > java-sources directory on the repository. The pattern should be
> > > something like {artifactId}-{version}-source.jar ; Check the eclipse
> > > plugin (1.10) for more details.
> > >
> > > I think we should first define a standard location and then create a
> > > maven one artifact handler for Java source code.
> > >
> > > Thanks,
> > > Stéphane
> > >
> > > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > > Hello Stephane,
> > > > I have the install and deploy goals implemented as well. it would be
> > > nice to
> > > > have the location somehow standardized, so that the sources don't
> appear
> > > at
> > > > many different places in the remote repository. I've been using the
> "
> > > src.jar"
> > > > location (made according to the "javadoc.jar" location) in the
> > > > maven-mevenide-plugin and the netbeans IDE integration so far.
> > > Unfortunately
> > > > there's not much sources in the remote repository just yet (neither
> is
> > > > javadocs :( ). I try uploading the sources for the mevenide project
> when
> > > I
> > > > do a release.
> > > > http://www.ibiblio.org/maven/mevenide/src.jars/
> > > >
> > > > regarding tools to download, I don't know about maven goals, but I
> can
> > > > download it from Netbeans (user can check the remote repositories
> for
> > > > javadocs and sources and mevenide will download it for him/her)
> > > >
> > > > Milos
> > > >
> > > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > >
> > > > > Hi Milos,
> > > > >
> > > > > I do have such a goal already as well. What I mean is a support of
> the
> > > > > artifact plugin for the java.src type. I want to be sure that it
> would
> > > > > deploy in the java-sources directory of the repository (so that
> this
> > > > > could be found by the eclipse plugin).
> > > > >
> > > > > Similarly, I would like to know if they are tools to *download*
> such
> > > > > artifact from the repository if they are not found in the local
> > > > > repository (for now the patch of MPECLIPSE-60 is quite a
> workaround).
> > > > >
> > > > > Cheers,
> > > > > Stéphane
> > > > >
> > > > > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > > > > not sure it's exactly what you are looking for but about a year
> ago
> > > I
> > > > > create
> > > > > > a bunch of goals to deal with creating source distributions,
> > > installing
> > > > > and
> > > > > > deploying them. I think I filed it as an enhancement for the
> dist
> > > plugin
> > > > > but
> > > > > > it's there since then untouched ;(
> > > > > > in the mean time i've added it to the maven-mevenide-plugin
> > > (a plugin
> > > > > that
> > > > > > I ship together with the mevenide-netbeans. it has many, quite
> > > > > unrelated
> > > > > > goals that are useful for the IDE integration.
> > > > > >
> > >
> http://mevenide.codehaus.org/maven-mevenide-plugin/changes-report.htmlhas
> > > > > > more details or check the sources at
> > > > > >
> > > http://cvs.mevenide.codehaus.org/maven-plugins/maven-mevenide-plugin/
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Milos
> > > > > >
> > > > > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > > >
> > > > > > > anyone?
> > > > > > >
> > > > > > > On 12/28/05, Stephane Nicoll <st...@gmail.com>
> wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > Our production is currently running m1.0.2 and I am planning
> to
> > > move
> > > > > > > > to 1.1 as soon as possible (is there a release date for 1.1by
> > > the
> > > > > > > > way?).
> > > > > > > >
> > > > > > > > We have used for a long time eclipse plugin 1.9 patched with
> > > > > > > > MPECLIPSE-60 (which basically download java sources from the
> > > > > > > > repository).
> > > > > > > >
> > > > > > > > Eclipse plugin 1.10 supports two locations for thoses
> sources:
> > > the
> > > > > src
> > > > > > > > directory and the new java-sources directory which is the
> one
> > > used
> > > > > > > > with m2.
> > > > > > > >
> > > > > > > > Having java-sources as an artifact is really needed here
> because
> > > > > > > > Eclipse plugin 1.10 is simply unable to download the
> > > java-sources
> > > > > from
> > > > > > > > the repository. The current patch localted in MECLIPSE-60 is
> > > unable
> > > > > to
> > > > > > > > refresh snapshots from the repository. We do have scripts to
> do
> > > such
> > > > > > > > things for jars/wars and the like. Any plan to add the
> support
> > > of
> > > > > java
> > > > > > > > sources?
> > > > > > > >
> > > > > > > > If anyone can point me to the right direction, I am willing
> to
> > > > > > > > implement this myself.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Stéphane
> > > > > > > >
> > > > > > > > --
> > > > > > > > .::You're welcome ::.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > .::You're welcome ::.
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > .::You're welcome ::.
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > .::You're welcome ::.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
>
>
> --
> .::You're welcome ::.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [m1] Support of Java source artifact planned?
Posted by Stephane Nicoll <st...@gmail.com>.
Milos,
Not a single clue about it. The only reason I see is explained in the
eclipse plugin changes:
<snip>
Java source location now defaults to
MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar
(standard location where source artifacts are deployed by the m2
source plugin in a legacy/m1 repository layout). The path
${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension}
is still supported for backward compatibility and it will be used
only if a file already exists at that location. Thanks to Fabrizio
Giustina.
<snip>
It seems this is the standard location used by the m2 source plugin. I
don't care about the final location actually: we need to standardize
this asap (at least before 1.1 final I would say). Keeping
compatibility with M2 seems important to me as well.
Regards,
Stéphane
On 1/2/06, Milos Kleint <mk...@gmail.com> wrote:
> what would be the full path in the remote repository then?
> mevenide/java-sources/mevenide-core-0.10-source.jar ?
>
> that doesn't conform to the <groupId>/<type>/<artifactid>-<version>.<type>
> pattern that the repository has otherwise.
> I think javadoc plugin had
> mevenide/javadocs/mevenide-core-0.10-javadoc.jarin some older version
> of the maven-javadoc-plugin but lately it has been
> changed to mevenide/javadoc.jars/mevenide-core-0.10.javadoc.jar
> I wonder what was the reason for the change? Maybe a javadoc-plugin
> developer could shed some light on that?
>
>
> Regards
>
> Milos
>
> On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
> >
> > Hey,
> >
> > It seems that the standard place to delpoy Java soures is in the
> > java-sources directory on the repository. The pattern should be
> > something like {artifactId}-{version}-source.jar ; Check the eclipse
> > plugin (1.10) for more details.
> >
> > I think we should first define a standard location and then create a
> > maven one artifact handler for Java source code.
> >
> > Thanks,
> > Stéphane
> >
> > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > Hello Stephane,
> > > I have the install and deploy goals implemented as well. it would be
> > nice to
> > > have the location somehow standardized, so that the sources don't appear
> > at
> > > many different places in the remote repository. I've been using the "
> > src.jar"
> > > location (made according to the "javadoc.jar" location) in the
> > > maven-mevenide-plugin and the netbeans IDE integration so far.
> > Unfortunately
> > > there's not much sources in the remote repository just yet (neither is
> > > javadocs :( ). I try uploading the sources for the mevenide project when
> > I
> > > do a release.
> > > http://www.ibiblio.org/maven/mevenide/src.jars/
> > >
> > > regarding tools to download, I don't know about maven goals, but I can
> > > download it from Netbeans (user can check the remote repositories for
> > > javadocs and sources and mevenide will download it for him/her)
> > >
> > > Milos
> > >
> > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > >
> > > > Hi Milos,
> > > >
> > > > I do have such a goal already as well. What I mean is a support of the
> > > > artifact plugin for the java.src type. I want to be sure that it would
> > > > deploy in the java-sources directory of the repository (so that this
> > > > could be found by the eclipse plugin).
> > > >
> > > > Similarly, I would like to know if they are tools to *download* such
> > > > artifact from the repository if they are not found in the local
> > > > repository (for now the patch of MPECLIPSE-60 is quite a workaround).
> > > >
> > > > Cheers,
> > > > Stéphane
> > > >
> > > > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > > > not sure it's exactly what you are looking for but about a year ago
> > I
> > > > create
> > > > > a bunch of goals to deal with creating source distributions,
> > installing
> > > > and
> > > > > deploying them. I think I filed it as an enhancement for the dist
> > plugin
> > > > but
> > > > > it's there since then untouched ;(
> > > > > in the mean time i've added it to the maven-mevenide-plugin
> > (a plugin
> > > > that
> > > > > I ship together with the mevenide-netbeans. it has many, quite
> > > > unrelated
> > > > > goals that are useful for the IDE integration.
> > > > >
> > http://mevenide.codehaus.org/maven-mevenide-plugin/changes-report.htmlhas
> > > > > more details or check the sources at
> > > > >
> > http://cvs.mevenide.codehaus.org/maven-plugins/maven-mevenide-plugin/
> > > > >
> > > > > Regards
> > > > >
> > > > > Milos
> > > > >
> > > > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > >
> > > > > > anyone?
> > > > > >
> > > > > > On 12/28/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > Our production is currently running m1.0.2 and I am planning to
> > move
> > > > > > > to 1.1 as soon as possible (is there a release date for 1.1 by
> > the
> > > > > > > way?).
> > > > > > >
> > > > > > > We have used for a long time eclipse plugin 1.9 patched with
> > > > > > > MPECLIPSE-60 (which basically download java sources from the
> > > > > > > repository).
> > > > > > >
> > > > > > > Eclipse plugin 1.10 supports two locations for thoses sources:
> > the
> > > > src
> > > > > > > directory and the new java-sources directory which is the one
> > used
> > > > > > > with m2.
> > > > > > >
> > > > > > > Having java-sources as an artifact is really needed here because
> > > > > > > Eclipse plugin 1.10 is simply unable to download the
> > java-sources
> > > > from
> > > > > > > the repository. The current patch localted in MECLIPSE-60 is
> > unable
> > > > to
> > > > > > > refresh snapshots from the repository. We do have scripts to do
> > such
> > > > > > > things for jars/wars and the like. Any plan to add the support
> > of
> > > > java
> > > > > > > sources?
> > > > > > >
> > > > > > > If anyone can point me to the right direction, I am willing to
> > > > > > > implement this myself.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Stéphane
> > > > > > >
> > > > > > > --
> > > > > > > .::You're welcome ::.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > .::You're welcome ::.
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > .::You're welcome ::.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > .::You're welcome ::.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] Support of Java source artifact planned?
Posted by Milos Kleint <mk...@gmail.com>.
what would be the full path in the remote repository then?
mevenide/java-sources/mevenide-core-0.10-source.jar ?
that doesn't conform to the <groupId>/<type>/<artifactid>-<version>.<type>
pattern that the repository has otherwise.
I think javadoc plugin had
mevenide/javadocs/mevenide-core-0.10-javadoc.jarin some older version
of the maven-javadoc-plugin but lately it has been
changed to mevenide/javadoc.jars/mevenide-core-0.10.javadoc.jar
I wonder what was the reason for the change? Maybe a javadoc-plugin
developer could shed some light on that?
Regards
Milos
On 1/2/06, Stephane Nicoll <st...@gmail.com> wrote:
>
> Hey,
>
> It seems that the standard place to delpoy Java soures is in the
> java-sources directory on the repository. The pattern should be
> something like {artifactId}-{version}-source.jar ; Check the eclipse
> plugin (1.10) for more details.
>
> I think we should first define a standard location and then create a
> maven one artifact handler for Java source code.
>
> Thanks,
> Stéphane
>
> On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > Hello Stephane,
> > I have the install and deploy goals implemented as well. it would be
> nice to
> > have the location somehow standardized, so that the sources don't appear
> at
> > many different places in the remote repository. I've been using the "
> src.jar"
> > location (made according to the "javadoc.jar" location) in the
> > maven-mevenide-plugin and the netbeans IDE integration so far.
> Unfortunately
> > there's not much sources in the remote repository just yet (neither is
> > javadocs :( ). I try uploading the sources for the mevenide project when
> I
> > do a release.
> > http://www.ibiblio.org/maven/mevenide/src.jars/
> >
> > regarding tools to download, I don't know about maven goals, but I can
> > download it from Netbeans (user can check the remote repositories for
> > javadocs and sources and mevenide will download it for him/her)
> >
> > Milos
> >
> > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > >
> > > Hi Milos,
> > >
> > > I do have such a goal already as well. What I mean is a support of the
> > > artifact plugin for the java.src type. I want to be sure that it would
> > > deploy in the java-sources directory of the repository (so that this
> > > could be found by the eclipse plugin).
> > >
> > > Similarly, I would like to know if they are tools to *download* such
> > > artifact from the repository if they are not found in the local
> > > repository (for now the patch of MPECLIPSE-60 is quite a workaround).
> > >
> > > Cheers,
> > > Stéphane
> > >
> > > On 12/29/05, Milos Kleint <mk...@gmail.com> wrote:
> > > > not sure it's exactly what you are looking for but about a year ago
> I
> > > create
> > > > a bunch of goals to deal with creating source distributions,
> installing
> > > and
> > > > deploying them. I think I filed it as an enhancement for the dist
> plugin
> > > but
> > > > it's there since then untouched ;(
> > > > in the mean time i've added it to the maven-mevenide-plugin
> (a plugin
> > > that
> > > > I ship together with the mevenide-netbeans. it has many, quite
> > > unrelated
> > > > goals that are useful for the IDE integration.
> > > >
> http://mevenide.codehaus.org/maven-mevenide-plugin/changes-report.htmlhas
> > > > more details or check the sources at
> > > >
> http://cvs.mevenide.codehaus.org/maven-plugins/maven-mevenide-plugin/
> > > >
> > > > Regards
> > > >
> > > > Milos
> > > >
> > > > On 12/29/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > >
> > > > > anyone?
> > > > >
> > > > > On 12/28/05, Stephane Nicoll <st...@gmail.com> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > Our production is currently running m1.0.2 and I am planning to
> move
> > > > > > to 1.1 as soon as possible (is there a release date for 1.1 by
> the
> > > > > > way?).
> > > > > >
> > > > > > We have used for a long time eclipse plugin 1.9 patched with
> > > > > > MPECLIPSE-60 (which basically download java sources from the
> > > > > > repository).
> > > > > >
> > > > > > Eclipse plugin 1.10 supports two locations for thoses sources:
> the
> > > src
> > > > > > directory and the new java-sources directory which is the one
> used
> > > > > > with m2.
> > > > > >
> > > > > > Having java-sources as an artifact is really needed here because
> > > > > > Eclipse plugin 1.10 is simply unable to download the
> java-sources
> > > from
> > > > > > the repository. The current patch localted in MECLIPSE-60 is
> unable
> > > to
> > > > > > refresh snapshots from the repository. We do have scripts to do
> such
> > > > > > things for jars/wars and the like. Any plan to add the support
> of
> > > java
> > > > > > sources?
> > > > > >
> > > > > > If anyone can point me to the right direction, I am willing to
> > > > > > implement this myself.
> > > > > >
> > > > > > Cheers,
> > > > > > Stéphane
> > > > > >
> > > > > > --
> > > > > > .::You're welcome ::.
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > .::You're welcome ::.
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > .::You're welcome ::.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
>
>
> --
> .::You're welcome ::.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>