You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Arnaud HERITIER <ah...@gmail.com> on 2008/03/28 01:37:31 UTC
[VOTE] Release Maven Eclipse plugin version 2.5.1
Hi,
Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
* [MECLIPSE-266] - plugin applies java facet to ear project
* [MECLIPSE-411] - manifest property usage is only for ogsi maifests
* [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
and not the EclipseProjectName
We also added a new feature :
* [MECLIPSE-405] - to-maven target should allow to strip qualifier
when creating artifacts from osgi bundles
There are still a lot of issues left in JIRA :
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
Staging repo :
http://people.apache.org/~aheritier/stage/repo/
Staging site (I'm uploading it) :
http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 5 days. I'll be back on wednesday to do the release if
the vote passes.
[ ] +1
[ ] +0
[ ] -1
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
ok thanks. I'll close the vote this evening and I'll release it.
I'll probably release a version 2.5.2 the next week.
cheers
arnaud
On Thu, Apr 3, 2008 at 10:32 AM, Jerome Lacoste
<je...@gmail.com> wrote:
> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
> > Hi Jerome,
> >
> > As you noticed, this plugin requires to be build with maven >= 2.0.8
> > because of some tests with encodings.
> > I'll add an enforcer rule as Benjamin proposed.
>
> I had added a patch to the issue hat uses the inbbuild POM
> requireMavenVersion instead of using the enforcer plugin. That worked
> for me.
>
> Cheers,
>
> Jerome
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Rahul Thakur <ra...@gmail.com>.
duh me! Please ignore; sorry about the noise. It was the root pom.
Rahul Thakur wrote:
>
> Is there a change in the recent release that is using 'build' folder for
> output by default? I generated Eclipse projects for Continuum and all
> projects have output folder set to 'build' in absence of any specified
> folders. The online plugin docs suggest otherwise; bug?
>
> Rahul
>
>
> Brian E. Fox wrote:
>> This only works on single module builds, the prerequisite field is not
>> inherited.
>>
>> -----Original Message-----
>> From: Jerome Lacoste [mailto:jerome.lacoste@gmail.com]
>> Sent: Thursday, April 03, 2008 4:33 AM
>> To: Maven Developers List
>> Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>>
>> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER<ah...@gmail.com>
>> wrote:
>>> Hi Jerome,
>>>
>>> As you noticed, this plugin requires to be build with maven>= 2.0.8
>>> because of some tests with encodings.
>>> I'll add an enforcer rule as Benjamin proposed.
>>
>> I had added a patch to the issue hat uses the inbbuild POM
>> requireMavenVersion instead of using the enforcer plugin. That worked
>> for me.
>>
>> Cheers,
>>
>> Jerome
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
I never had this problem.
I don't think we changed something in this code.
Can you open an issue.
I'll investigate for 2.5.2
Arnaud
On Tue, Apr 8, 2008 at 9:23 AM, Rahul Thakur
<ra...@gmail.com> wrote:
>
> Is there a change in the recent release that is using 'build' folder for
> output by default? I generated Eclipse projects for Continuum and all
> projects have output folder set to 'build' in absence of any specified
> folders. The online plugin docs suggest otherwise; bug?
>
> Rahul
>
>
>
>
> Brian E. Fox wrote:
>
> > This only works on single module builds, the prerequisite field is not
> > inherited.
> >
> > -----Original Message-----
> > From: Jerome Lacoste [mailto:jerome.lacoste@gmail.com]
> > Sent: Thursday, April 03, 2008 4:33 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> >
> > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER<ah...@gmail.com>
> > wrote:
> >
> >
> > > Hi Jerome,
> > >
> > > As you noticed, this plugin requires to be build with maven>= 2.0.8
> > > because of some tests with encodings.
> > > I'll add an enforcer rule as Benjamin proposed.
> > >
> > >
> >
> > I had added a patch to the issue hat uses the inbbuild POM
> > requireMavenVersion instead of using the enforcer plugin. That worked
> > for me.
> >
> > Cheers,
> >
> > Jerome
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Rahul Thakur <ra...@gmail.com>.
Is there a change in the recent release that is using 'build' folder for
output by default? I generated Eclipse projects for Continuum and all
projects have output folder set to 'build' in absence of any specified
folders. The online plugin docs suggest otherwise; bug?
Rahul
Brian E. Fox wrote:
> This only works on single module builds, the prerequisite field is not
> inherited.
>
> -----Original Message-----
> From: Jerome Lacoste [mailto:jerome.lacoste@gmail.com]
> Sent: Thursday, April 03, 2008 4:33 AM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>
> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER<ah...@gmail.com>
> wrote:
>
>> Hi Jerome,
>>
>> As you noticed, this plugin requires to be build with maven>= 2.0.8
>> because of some tests with encodings.
>> I'll add an enforcer rule as Benjamin proposed.
>>
>
> I had added a patch to the issue hat uses the inbbuild POM
> requireMavenVersion instead of using the enforcer plugin. That worked
> for me.
>
> Cheers,
>
> Jerome
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
This only works on single module builds, the prerequisite field is not
inherited.
-----Original Message-----
From: Jerome Lacoste [mailto:jerome.lacoste@gmail.com]
Sent: Thursday, April 03, 2008 4:33 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
wrote:
> Hi Jerome,
>
> As you noticed, this plugin requires to be build with maven >= 2.0.8
> because of some tests with encodings.
> I'll add an enforcer rule as Benjamin proposed.
I had added a patch to the issue hat uses the inbbuild POM
requireMavenVersion instead of using the enforcer plugin. That worked
for me.
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Lukas Theussl <lt...@apache.org>.
+1 :)
-Lukas
Arnaud HERITIER wrote:
> I have not enough PMCs votes to launch the release. If some of you can test it.
> thx
>
> cheers
>
> arnaud
>
> On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
>>Ok that's right. The prerequisite is intended for tools and isn't
>> inherited (making it not good for normal builds) but does apply at
>> runtime. In this instance, the prerequisite is the most appropriate way
>> to require the maven version.
>>
>>
>> -----Original Message-----
>> From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
>> Sent: Thursday, April 03, 2008 6:08 AM
>> To: Maven Developers List
>> Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>>
>>
>>
>>Hi,
>>
>> the requireMavenVersion also applies to the runtime, but 2.0.8 is just
>> required for the testing during the build. As far as i know not for the
>> runtime. We use the plugin in a lot of projects that are locked to maven
>> 2.0.7.
>>
>> So please limit it only for the build time.
>>
>> regards,
>> Ritchie
>>
>>
>>
>> Jerome Lacoste wrote:
>> > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
>> wrote:
>> >> Hi Jerome,
>> >>
>> >> As you noticed, this plugin requires to be build with maven >=
>> 2.0.8
>> >> because of some tests with encodings.
>> >> I'll add an enforcer rule as Benjamin proposed.
>> >
>> > I had added a patch to the issue hat uses the inbbuild POM
>> > requireMavenVersion instead of using the enforcer plugin. That worked
>> > for me.
>> >
>> > Cheers,
>> >
>> > Jerome
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Siarhei Dudzin <si...@gmail.com>.
+1
On Fri, Apr 4, 2008 at 9:22 PM, Arnaud HERITIER <ah...@gmail.com> wrote:
> Actually I have only :
> 1 PMC : myself
> 1 Committer : Nicolas DE LOOF
> 1 User : Richard VAN NIEUWENHOVEN
>
> Anyone else ? (I'm already working on 2.5.2 ;-) )
>
> Arnaud
>
> On Fri, Apr 4, 2008 at 12:39 AM, Arnaud HERITIER <ah...@gmail.com>
> wrote:
> > I have not enough PMCs votes to launch the release. If some of you can
> test it.
> > thx
> >
> > cheers
> >
> > arnaud
> >
> >
> >
> > On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu>
> wrote:
> > > Ok that's right. The prerequisite is intended for tools and isn't
> > > inherited (making it not good for normal builds) but does apply at
> > > runtime. In this instance, the prerequisite is the most appropriate
> way
> > > to require the maven version.
> > >
> > >
> > > -----Original Message-----
> > > From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> > > Sent: Thursday, April 03, 2008 6:08 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> > >
> > >
> > >
> > > Hi,
> > >
> > > the requireMavenVersion also applies to the runtime, but 2.0.8 is
> just
> > > required for the testing during the build. As far as i know not for
> the
> > > runtime. We use the plugin in a lot of projects that are locked to
> maven
> > > 2.0.7.
> > >
> > > So please limit it only for the build time.
> > >
> > > regards,
> > > Ritchie
> > >
> > >
> > >
> > > Jerome Lacoste wrote:
> > > > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <
> aheritier@gmail.com>
> > > wrote:
> > > >> Hi Jerome,
> > > >>
> > > >> As you noticed, this plugin requires to be build with maven >=
> > > 2.0.8
> > > >> because of some tests with encodings.
> > > >> I'll add an enforcer rule as Benjamin proposed.
> > > >
> > > > I had added a patch to the issue hat uses the inbbuild POM
> > > > requireMavenVersion instead of using the enforcer plugin. That
> worked
> > > > for me.
> > > >
> > > > Cheers,
> > > >
> > > > Jerome
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> >
> >
> >
> > --
> > ..........................................................
> > Arnaud HERITIER
> > ..........................................................
> > OCTO Technology - aheritier AT octo DOT com
> > www.octo.com | blog.octo.com
> > ..........................................................
> > ASF - aheritier AT apache DOT org
> > www.apache.org | maven.apache.org
> > ...........................................................
> >
>
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
You have to become a PMC member of the project :
http://www.apache.org/foundation/how-it-works.html#pmc-members
cheers
Arnaud
On Fri, Apr 4, 2008 at 9:30 PM, Stefan Bley <st...@saxsys.de> wrote:
> I would like to vote for it. How do I do this?
>
> Stefan
>
> Arnaud HERITIER schrieb:
>
>
>
> > Actually I have only :
> > 1 PMC : myself
> > 1 Committer : Nicolas DE LOOF
> > 1 User : Richard VAN NIEUWENHOVEN
> >
> > Anyone else ? (I'm already working on 2.5.2 ;-) )
> >
> > Arnaud
> >
> > On Fri, Apr 4, 2008 at 12:39 AM, Arnaud HERITIER <ah...@gmail.com>
> wrote:
> >
> >
> > > I have not enough PMCs votes to launch the release. If some of you can
> test it.
> > > thx
> > >
> > > cheers
> > >
> > > arnaud
> > >
> > >
> > >
> > > On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu>
> wrote:
> > > > Ok that's right. The prerequisite is intended for tools and isn't
> > > > inherited (making it not good for normal builds) but does apply at
> > > > runtime. In this instance, the prerequisite is the most appropriate
> way
> > > > to require the maven version.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> > > > Sent: Thursday, April 03, 2008 6:08 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > the requireMavenVersion also applies to the runtime, but 2.0.8 is
> just
> > > > required for the testing during the build. As far as i know not for
> the
> > > > runtime. We use the plugin in a lot of projects that are locked to
> maven
> > > > 2.0.7.
> > > >
> > > > So please limit it only for the build time.
> > > >
> > > > regards,
> > > > Ritchie
> > > >
> > > >
> > > >
> > > > Jerome Lacoste wrote:
> > > > > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER
> <ah...@gmail.com>
> > > > wrote:
> > > > >> Hi Jerome,
> > > > >>
> > > > >> As you noticed, this plugin requires to be build with maven >=
> > > > 2.0.8
> > > > >> because of some tests with encodings.
> > > > >> I'll add an enforcer rule as Benjamin proposed.
> > > > >
> > > > > I had added a patch to the issue hat uses the inbbuild POM
> > > > > requireMavenVersion instead of using the enforcer plugin. That
> worked
> > > > > for me.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Jerome
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > ..........................................................
> > > Arnaud HERITIER
> > > ..........................................................
> > > OCTO Technology - aheritier AT octo DOT com
> > > www.octo.com | blog.octo.com
> > > ..........................................................
> > > ASF - aheritier AT apache DOT org
> > > www.apache.org | maven.apache.org
> > > ...........................................................
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Stefan Bley <st...@saxsys.de>.
I would like to vote for it. How do I do this?
Stefan
Arnaud HERITIER schrieb:
> Actually I have only :
> 1 PMC : myself
> 1 Committer : Nicolas DE LOOF
> 1 User : Richard VAN NIEUWENHOVEN
>
> Anyone else ? (I'm already working on 2.5.2 ;-) )
>
> Arnaud
>
> On Fri, Apr 4, 2008 at 12:39 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
>
>> I have not enough PMCs votes to launch the release. If some of you can test it.
>> thx
>>
>> cheers
>>
>> arnaud
>>
>>
>>
>> On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
>> > Ok that's right. The prerequisite is intended for tools and isn't
>> > inherited (making it not good for normal builds) but does apply at
>> > runtime. In this instance, the prerequisite is the most appropriate way
>> > to require the maven version.
>> >
>> >
>> > -----Original Message-----
>> > From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
>> > Sent: Thursday, April 03, 2008 6:08 AM
>> > To: Maven Developers List
>> > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>> >
>> >
>> >
>> > Hi,
>> >
>> > the requireMavenVersion also applies to the runtime, but 2.0.8 is just
>> > required for the testing during the build. As far as i know not for the
>> > runtime. We use the plugin in a lot of projects that are locked to maven
>> > 2.0.7.
>> >
>> > So please limit it only for the build time.
>> >
>> > regards,
>> > Ritchie
>> >
>> >
>> >
>> > Jerome Lacoste wrote:
>> > > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
>> > wrote:
>> > >> Hi Jerome,
>> > >>
>> > >> As you noticed, this plugin requires to be build with maven >=
>> > 2.0.8
>> > >> because of some tests with encodings.
>> > >> I'll add an enforcer rule as Benjamin proposed.
>> > >
>> > > I had added a patch to the issue hat uses the inbbuild POM
>> > > requireMavenVersion instead of using the enforcer plugin. That worked
>> > > for me.
>> > >
>> > > Cheers,
>> > >
>> > > Jerome
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>> > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>>
>>
>>
>>
>>
>> --
>> ..........................................................
>> Arnaud HERITIER
>> ..........................................................
>> OCTO Technology - aheritier AT octo DOT com
>> www.octo.com | blog.octo.com
>> ..........................................................
>> ASF - aheritier AT apache DOT org
>> www.apache.org | maven.apache.org
>> ...........................................................
>>
>>
>
>
>
>
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
thanks, the vote passed :
3 PMCs : Arnaud HERITIER, Lukas THEUSSL, Olivier LAMY
1 Committer : Nicolas DE LOOF
2 Users : Siarhei DUDZIN, Richard VAN NIEUWENHOVEN
The release will be deployed in few hours
Arnaud
On Fri, Apr 4, 2008 at 10:48 PM, Olivier Lamy <ol...@apache.org> wrote:
> +1
> --
> Olivier
>
> 2008/4/4, Arnaud HERITIER <ah...@gmail.com>:
>
>
> > Actually I have only :
> > 1 PMC : myself
> > 1 Committer : Nicolas DE LOOF
> > 1 User : Richard VAN NIEUWENHOVEN
> >
> > Anyone else ? (I'm already working on 2.5.2 ;-) )
> >
> > Arnaud
> >
> > On Fri, Apr 4, 2008 at 12:39 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
> > > I have not enough PMCs votes to launch the release. If some of you can test it.
> > > thx
> > >
> > > cheers
> > >
> > > arnaud
> > >
> > >
> > >
> > > On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > Ok that's right. The prerequisite is intended for tools and isn't
> > > > inherited (making it not good for normal builds) but does apply at
> > > > runtime. In this instance, the prerequisite is the most appropriate way
> > > > to require the maven version.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> > > > Sent: Thursday, April 03, 2008 6:08 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > the requireMavenVersion also applies to the runtime, but 2.0.8 is just
> > > > required for the testing during the build. As far as i know not for the
> > > > runtime. We use the plugin in a lot of projects that are locked to maven
> > > > 2.0.7.
> > > >
> > > > So please limit it only for the build time.
> > > >
> > > > regards,
> > > > Ritchie
> > > >
> > > >
> > > >
> > > > Jerome Lacoste wrote:
> > > > > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
> > > > wrote:
> > > > >> Hi Jerome,
> > > > >>
> > > > >> As you noticed, this plugin requires to be build with maven >=
> > > > 2.0.8
> > > > >> because of some tests with encodings.
> > > > >> I'll add an enforcer rule as Benjamin proposed.
> > > > >
> > > > > I had added a patch to the issue hat uses the inbbuild POM
> > > > > requireMavenVersion instead of using the enforcer plugin. That worked
> > > > > for me.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Jerome
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > ..........................................................
> > > Arnaud HERITIER
> > > ..........................................................
> > > OCTO Technology - aheritier AT octo DOT com
> > > www.octo.com | blog.octo.com
> > > ..........................................................
> > > ASF - aheritier AT apache DOT org
> > > www.apache.org | maven.apache.org
> > > ...........................................................
> > >
> >
> >
> >
> > --
> > ..........................................................
> > Arnaud HERITIER
> > ..........................................................
> > OCTO Technology - aheritier AT octo DOT com
> > www.octo.com | blog.octo.com
> > ..........................................................
> > ASF - aheritier AT apache DOT org
> > www.apache.org | maven.apache.org
> > ...........................................................
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Olivier Lamy <ol...@apache.org>.
+1
--
Olivier
2008/4/4, Arnaud HERITIER <ah...@gmail.com>:
> Actually I have only :
> 1 PMC : myself
> 1 Committer : Nicolas DE LOOF
> 1 User : Richard VAN NIEUWENHOVEN
>
> Anyone else ? (I'm already working on 2.5.2 ;-) )
>
> Arnaud
>
> On Fri, Apr 4, 2008 at 12:39 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
> > I have not enough PMCs votes to launch the release. If some of you can test it.
> > thx
> >
> > cheers
> >
> > arnaud
> >
> >
> >
> > On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > Ok that's right. The prerequisite is intended for tools and isn't
> > > inherited (making it not good for normal builds) but does apply at
> > > runtime. In this instance, the prerequisite is the most appropriate way
> > > to require the maven version.
> > >
> > >
> > > -----Original Message-----
> > > From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> > > Sent: Thursday, April 03, 2008 6:08 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> > >
> > >
> > >
> > > Hi,
> > >
> > > the requireMavenVersion also applies to the runtime, but 2.0.8 is just
> > > required for the testing during the build. As far as i know not for the
> > > runtime. We use the plugin in a lot of projects that are locked to maven
> > > 2.0.7.
> > >
> > > So please limit it only for the build time.
> > >
> > > regards,
> > > Ritchie
> > >
> > >
> > >
> > > Jerome Lacoste wrote:
> > > > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
> > > wrote:
> > > >> Hi Jerome,
> > > >>
> > > >> As you noticed, this plugin requires to be build with maven >=
> > > 2.0.8
> > > >> because of some tests with encodings.
> > > >> I'll add an enforcer rule as Benjamin proposed.
> > > >
> > > > I had added a patch to the issue hat uses the inbbuild POM
> > > > requireMavenVersion instead of using the enforcer plugin. That worked
> > > > for me.
> > > >
> > > > Cheers,
> > > >
> > > > Jerome
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> >
> >
> >
> > --
> > ..........................................................
> > Arnaud HERITIER
> > ..........................................................
> > OCTO Technology - aheritier AT octo DOT com
> > www.octo.com | blog.octo.com
> > ..........................................................
> > ASF - aheritier AT apache DOT org
> > www.apache.org | maven.apache.org
> > ...........................................................
> >
>
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Actually I have only :
1 PMC : myself
1 Committer : Nicolas DE LOOF
1 User : Richard VAN NIEUWENHOVEN
Anyone else ? (I'm already working on 2.5.2 ;-) )
Arnaud
On Fri, Apr 4, 2008 at 12:39 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
> I have not enough PMCs votes to launch the release. If some of you can test it.
> thx
>
> cheers
>
> arnaud
>
>
>
> On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Ok that's right. The prerequisite is intended for tools and isn't
> > inherited (making it not good for normal builds) but does apply at
> > runtime. In this instance, the prerequisite is the most appropriate way
> > to require the maven version.
> >
> >
> > -----Original Message-----
> > From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> > Sent: Thursday, April 03, 2008 6:08 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
> >
> >
> >
> > Hi,
> >
> > the requireMavenVersion also applies to the runtime, but 2.0.8 is just
> > required for the testing during the build. As far as i know not for the
> > runtime. We use the plugin in a lot of projects that are locked to maven
> > 2.0.7.
> >
> > So please limit it only for the build time.
> >
> > regards,
> > Ritchie
> >
> >
> >
> > Jerome Lacoste wrote:
> > > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
> > wrote:
> > >> Hi Jerome,
> > >>
> > >> As you noticed, this plugin requires to be build with maven >=
> > 2.0.8
> > >> because of some tests with encodings.
> > >> I'll add an enforcer rule as Benjamin proposed.
> > >
> > > I had added a patch to the issue hat uses the inbbuild POM
> > > requireMavenVersion instead of using the enforcer plugin. That worked
> > > for me.
> > >
> > > Cheers,
> > >
> > > Jerome
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
>
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
I have not enough PMCs votes to launch the release. If some of you can test it.
thx
cheers
arnaud
On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Ok that's right. The prerequisite is intended for tools and isn't
> inherited (making it not good for normal builds) but does apply at
> runtime. In this instance, the prerequisite is the most appropriate way
> to require the maven version.
>
>
> -----Original Message-----
> From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> Sent: Thursday, April 03, 2008 6:08 AM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
>
>
>
> Hi,
>
> the requireMavenVersion also applies to the runtime, but 2.0.8 is just
> required for the testing during the build. As far as i know not for the
> runtime. We use the plugin in a lot of projects that are locked to maven
> 2.0.7.
>
> So please limit it only for the build time.
>
> regards,
> Ritchie
>
>
>
> Jerome Lacoste wrote:
> > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
> wrote:
> >> Hi Jerome,
> >>
> >> As you noticed, this plugin requires to be build with maven >=
> 2.0.8
> >> because of some tests with encodings.
> >> I'll add an enforcer rule as Benjamin proposed.
> >
> > I had added a patch to the issue hat uses the inbbuild POM
> > requireMavenVersion instead of using the enforcer plugin. That worked
> > for me.
> >
> > Cheers,
> >
> > Jerome
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Ok that's right. The prerequisite is intended for tools and isn't
inherited (making it not good for normal builds) but does apply at
runtime. In this instance, the prerequisite is the most appropriate way
to require the maven version.
-----Original Message-----
From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
Sent: Thursday, April 03, 2008 6:08 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know not for the
runtime. We use the plugin in a lot of projects that are locked to maven
2.0.7.
So please limit it only for the build time.
regards,
Ritchie
Jerome Lacoste wrote:
> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com>
wrote:
>> Hi Jerome,
>>
>> As you noticed, this plugin requires to be build with maven >=
2.0.8
>> because of some tests with encodings.
>> I'll add an enforcer rule as Benjamin proposed.
>
> I had added a patch to the issue hat uses the inbbuild POM
> requireMavenVersion instead of using the enforcer plugin. That worked
> for me.
>
> Cheers,
>
> Jerome
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
Hi,
the requireMavenVersion also applies to the runtime, but 2.0.8 is just
required for the testing during the build. As far as i know not for the
runtime. We use the plugin in a lot of projects that are locked to maven
2.0.7.
So please limit it only for the build time.
regards,
Ritchie
Jerome Lacoste wrote:
> On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
>> Hi Jerome,
>>
>> As you noticed, this plugin requires to be build with maven >= 2.0.8
>> because of some tests with encodings.
>> I'll add an enforcer rule as Benjamin proposed.
>
> I had added a patch to the issue hat uses the inbbuild POM
> requireMavenVersion instead of using the enforcer plugin. That worked
> for me.
>
> Cheers,
>
> Jerome
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Jerome Lacoste <je...@gmail.com>.
On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <ah...@gmail.com> wrote:
> Hi Jerome,
>
> As you noticed, this plugin requires to be build with maven >= 2.0.8
> because of some tests with encodings.
> I'll add an enforcer rule as Benjamin proposed.
I had added a patch to the issue hat uses the inbbuild POM
requireMavenVersion instead of using the enforcer plugin. That worked
for me.
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi Jerome,
As you noticed, this plugin requires to be build with maven >= 2.0.8
because of some tests with encodings.
I'll add an enforcer rule as Benjamin proposed.
Arnaud
On Mon, Mar 31, 2008 at 12:55 PM, Jerome Lacoste
<je...@gmail.com> wrote:
> On Fri, Mar 28, 2008 at 2:37 AM, Arnaud HERITIER <ah...@gmail.com>
> wrote:
>
>
> > Hi,
> >
> > Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> > * [MECLIPSE-266] - plugin applies java facet to ear project
> > * [MECLIPSE-411] - manifest property usage is only for ogsi maifests
> > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> > and not the EclipseProjectName
> > We also added a new feature :
> > * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> > when creating artifacts from osgi bundles
> >
> > There are still a lot of issues left in JIRA :
> >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> >
> > Staging repo :
>
> > http://people.apache.org/~aheritier/stage/repo/<http://people.apache.org/%7Eaheritier/stage/repo/>
>
>
> Haven't tried the staged plugin itself, but building trunk doesn't work for
> me.
>
> http://jira.codehaus.org/browse/MECLIPSE-416
>
> I am looking into the problems to find more information.
>
> Results :
>
> Failed tests:
> testProject33(org.apache.maven.plugin.eclipse.EclipsePluginTest)
>
> Tests in error:
> testProject16(org.apache.maven.plugin.eclipse.EclipsePluginTest)
> testProject17(org.apache.maven.plugin.eclipse.EclipsePluginTest)
> testMECLIPSE_56_encoding(org.apache.maven.plugin.eclipse.EclipsePluginTest
> )
>
> Tests run: 91, Failures: 1, Errors: 3, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
>
> J
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Jerome Lacoste <je...@gmail.com>.
On Fri, Mar 28, 2008 at 2:37 AM, Arnaud HERITIER <ah...@gmail.com>
wrote:
> Hi,
>
> Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> * [MECLIPSE-266] - plugin applies java facet to ear project
> * [MECLIPSE-411] - manifest property usage is only for ogsi maifests
> * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> and not the EclipseProjectName
> We also added a new feature :
> * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> when creating artifacts from osgi bundles
>
> There are still a lot of issues left in JIRA :
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
>
> Staging repo :
> http://people.apache.org/~aheritier/stage/repo/<http://people.apache.org/%7Eaheritier/stage/repo/>
Haven't tried the staged plugin itself, but building trunk doesn't work for
me.
http://jira.codehaus.org/browse/MECLIPSE-416
I am looking into the problems to find more information.
Results :
Failed tests:
testProject33(org.apache.maven.plugin.eclipse.EclipsePluginTest)
Tests in error:
testProject16(org.apache.maven.plugin.eclipse.EclipsePluginTest)
testProject17(org.apache.maven.plugin.eclipse.EclipsePluginTest)
testMECLIPSE_56_encoding(org.apache.maven.plugin.eclipse.EclipsePluginTest
)
Tests run: 91, Failures: 1, Errors: 3, Skipped: 0
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
J
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
It's on my todo list.
I began to prepare a big refactoring/rewrite of this plugin.
it will be a 3.0. I'll give more details about what I have in mind in some weeks
cheers
arnaud
On Fri, Mar 28, 2008 at 6:03 PM, nicolas de loof <ni...@apache.org> wrote:
> +1
>
> please cleanup the plugin that is allready not so simple to maintain ;-p
>
>
> 2008/3/28, Richard van Nieuwenhoven <ri...@gmx.at>:
>
>
> >
> > Hi,
> >
> > just created the JIRA http://jira.codehaus.org/browse/MECLIPSE-415 and
> > attached the patch. This problem seems to be connected to the wrongly
> > used executedProject parameter and maven 2.0.9.
> >
> > The stage thing is that "testProject11" fails when i remove the usage of
> > the executedProject.
> >
> > Also i am in favour to delete the code in the validate method of the
> > EclipsePlugin that allows to use an other directory for the settings as
> > the base directory. This code can only work for very very simple
> > projects, so we should just delete it. And make the eclipseProjectDir =
> > eclipse.projectDir readonly and set it to ${basedir}
> >
> > Ritchie
> >
> > Arnaud HERITIER wrote:
> > > Ok. Thx a lot. I'll fix it with the executedProject the next week.
> > >
> > > Arnaud
> > >
> > > On Fri, Mar 28, 2008 at 12:16 PM, Richard van Nieuwenhoven <ni...@cfc.at>
> > wrote:
> > >> hmmm, that seems to be a relict of the old usage of the workspace
> > >> variable usage (that Arnaud removed). Later today i will create an
> > jira
> > >> issue and a patch. (this should not be hard to find).
> > >>
> > >> Ritchie
> > >>
> > >>
> > >>
> > >> nicolas de loof wrote:
> > >> > Also had this issue since 2.5-SNAPSHOTs, but never took the time to
> > report
> > >> > in Jira :-/
> > >> >
> > >> > Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
> > >> > configuration solves this, but this is only a workaround.
> > >> >
> > >> > Nicolas.
> > >> >
> > >> > 2008/3/28, Arnaud HERITIER <ah...@gmail.com>:
> > >> >> Hi all,
> > >> >>
> > >> >> I just discovered a bug, or an hidden feature in 2.5 :-)
> > >> >> Richard, I think it is related to MECLIPSE-344.
> > >> >>
> > >> >> I store my projects in a directory which isn't my eclipse
> > workspace.
> > >> >> If I define the workspace attribute to be able to read its
> > settings,
> > >> >> when I call eclipse:eclipse, my projects settings are written in
> > the
> > >> >> workspace and not in each project's directory.
> > >> >> Is it what you expected ?
> > >> >>
> > >> >> Arnaud
> > >> >>
> > >> >> N.B. : I will not be able to publish a new version before my
> > departure
> > >> >> this evening, thus I'll prepare a 1.5.2 just after this one if we
> > >> >> decide that we have to fix the plugin (what I'm thinking)
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <
> > nicolas@apache.org>
> > >> >> wrote:
> > >> >>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with
> > latest
> > >> >> maven
> > >> >>> 2.0.9 RC4 :
> > >> >>>
> > >> >>> I've set a custom profile in my corporate POM to setup eclipse.
> > It runs
> > >> >> the
> > >> >>> validate phase and attach eclipse:eclipse plugin goal to this
> > phase.
> > >> >> Using
> > >> >>> this, a fresh SVN checkout can configure eclipse by running "mvn
> > >> >> -Psetup"
> > >> >>> <profile>
> > >> >>> <id>setup</id>
> > >> >>> <build>
> > >> >>> <defaultGoal>validate</defaultGoal>
> > >> >>> <plugins>
> > >> >>> <plugin>
> > >> >>> <artifactId>maven-eclipse-plugin</artifactId>
> > >> >>> <executions>
> > >> >>> <execution>
> > >> >>> <id>setup</id>
> > >> >>> <goals>
> > >> >>> <goal>eclipse</goal>
> > >> >>> </goals>
> > >> >>> <phase>validate</phase>
> > >> >>> </execution>
> > >> >>> </executions>
> > >> >>> </plugin>
> > >> >>>
> > >> >>> I get this error :
> > >> >>>
> > >> >>> [INFO]
> >
> > >> >>> ------------------------------------------------------------------------
> > >> >>> [ERROR] BUILD ERROR
> > >> >>> [INFO]
> >
> > >> >>> ------------------------------------------------------------------------
> > >> >>> [INFO] There must be a POM in the current working directory for
> > the
> > >> >> Eclipse
> > >> >>> plugin to work.
> > >> >>> [INFO]
> >
> > >> >>> ------------------------------------------------------------------------
> > >> >>>
> > >> >>> The EclispePlugin.validate() method fails on
> > >> >>>
> > >> >>> if ( executedProject.getFile() == null ||
> > >> >>> !executedProject.getFile().exists() ) ...
> > >> >>>
> > >> >>> What is the distinction between "executedProject" and "project"
> > from a
> > >> >>> plugin point of view ?
> > >> >>> This seem to have changed in maven 2.0.9.
> > >> >>>
> > >> >>> My use case is not really standard, but this may suggest some
> > >> >> regression
> > >> >>> either in maven 2.0.9 or the eclipse plugin.
> > >> >>>
> > >> >>> Nicolas
> > >> >>>
> > >> >>>
> > >> >>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
> > >> >>>
> > >> >>>
> > >> >>> > Hi,
> > >> >>> >
> > >> >>> > here is my +1
> > >> >>> >
> > >> >>> > Thanks for the fast release!
> > >> >>> >
> > >> >>> > Ritchie
> > >> >>> >
> > >> >>> > Arnaud HERITIER wrote:
> > >> >>> > > Hi,
> > >> >>> > >
> > >> >>> > > Since the 2.5 release we did 10 days ago, we solved 3
> > annoying
> > >> >> issues:
> > >> >>> > > * [MECLIPSE-266] - plugin applies java facet to ear
> > project
> > >> >>> > > * [MECLIPSE-411] - manifest property usage is only for
> > ogsi
> > >> >> maifests
> > >> >>> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the
> > artifact
> > >> >> id
> > >> >>> > > and not the EclipseProjectName
> > >> >>> > > We also added a new feature :
> > >> >>> > > * [MECLIPSE-405] - to-maven target should allow to strip
> > >> >> qualifier
> > >> >>> > > when creating artifacts from osgi bundles
> > >> >>> > >
> > >> >>> > > There are still a lot of issues left in JIRA :
> > >> >>> > >
> > >> >>> >
> > >> >>
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> > >> >>> > >
> > >> >>> > > Staging repo :
> > >> >>> > > http://people.apache.org/~aheritier/stage/repo/
> > >> >>> > >
> > >> >>> > > Staging site (I'm uploading it) :
> > >> >>> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> > >> >>> > >
> > >> >>> > > Guide to testing staged releases:
> > >> >>> > >
> > >> >>
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> > >> >>> > >
> > >> >>> > > Vote open for 5 days. I'll be back on wednesday to do the
> > release
> > >> >> if
> > >> >>> > > the vote passes.
> > >> >>> > >
> > >> >>> > > [ ] +1
> > >> >>> > > [ ] +0
> > >> >>> > > [ ] -1
> > >> >>> > >
> > >> >>> >
> > >> >>> >
> > >> >>> >
> > ---------------------------------------------------------------------
> > >> >>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> >>> > For additional commands, e-mail: dev-help@maven.apache.org
> > >> >>> >
> > >> >>> >
> > >> >>>
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >> ..........................................................
> > >> >>
> > >> >> Arnaud HERITIER
> > >> >> ..........................................................
> > >> >> OCTO Technology - aheritier AT octo DOT com
> > >> >> www.octo.com | blog.octo.com
> > >> >> ..........................................................
> > >> >> ASF - aheritier AT apache DOT org
> > >> >> www.apache.org | maven.apache.org
> > >> >> ...........................................................
> > >> >>
> > >> >>
> > >> >>
> > ---------------------------------------------------------------------
> > >> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> >> For additional commands, e-mail: dev-help@maven.apache.org
> > >> >>
> > >> >>
> > >> >
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by nicolas de loof <ni...@apache.org>.
+1
please cleanup the plugin that is allready not so simple to maintain ;-p
2008/3/28, Richard van Nieuwenhoven <ri...@gmx.at>:
>
> Hi,
>
> just created the JIRA http://jira.codehaus.org/browse/MECLIPSE-415 and
> attached the patch. This problem seems to be connected to the wrongly
> used executedProject parameter and maven 2.0.9.
>
> The stage thing is that "testProject11" fails when i remove the usage of
> the executedProject.
>
> Also i am in favour to delete the code in the validate method of the
> EclipsePlugin that allows to use an other directory for the settings as
> the base directory. This code can only work for very very simple
> projects, so we should just delete it. And make the eclipseProjectDir =
> eclipse.projectDir readonly and set it to ${basedir}
>
> Ritchie
>
> Arnaud HERITIER wrote:
> > Ok. Thx a lot. I'll fix it with the executedProject the next week.
> >
> > Arnaud
> >
> > On Fri, Mar 28, 2008 at 12:16 PM, Richard van Nieuwenhoven <ni...@cfc.at>
> wrote:
> >> hmmm, that seems to be a relict of the old usage of the workspace
> >> variable usage (that Arnaud removed). Later today i will create an
> jira
> >> issue and a patch. (this should not be hard to find).
> >>
> >> Ritchie
> >>
> >>
> >>
> >> nicolas de loof wrote:
> >> > Also had this issue since 2.5-SNAPSHOTs, but never took the time to
> report
> >> > in Jira :-/
> >> >
> >> > Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
> >> > configuration solves this, but this is only a workaround.
> >> >
> >> > Nicolas.
> >> >
> >> > 2008/3/28, Arnaud HERITIER <ah...@gmail.com>:
> >> >> Hi all,
> >> >>
> >> >> I just discovered a bug, or an hidden feature in 2.5 :-)
> >> >> Richard, I think it is related to MECLIPSE-344.
> >> >>
> >> >> I store my projects in a directory which isn't my eclipse
> workspace.
> >> >> If I define the workspace attribute to be able to read its
> settings,
> >> >> when I call eclipse:eclipse, my projects settings are written in
> the
> >> >> workspace and not in each project's directory.
> >> >> Is it what you expected ?
> >> >>
> >> >> Arnaud
> >> >>
> >> >> N.B. : I will not be able to publish a new version before my
> departure
> >> >> this evening, thus I'll prepare a 1.5.2 just after this one if we
> >> >> decide that we have to fix the plugin (what I'm thinking)
> >> >>
> >> >>
> >> >>
> >> >> On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <
> nicolas@apache.org>
> >> >> wrote:
> >> >>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with
> latest
> >> >> maven
> >> >>> 2.0.9 RC4 :
> >> >>>
> >> >>> I've set a custom profile in my corporate POM to setup eclipse.
> It runs
> >> >> the
> >> >>> validate phase and attach eclipse:eclipse plugin goal to this
> phase.
> >> >> Using
> >> >>> this, a fresh SVN checkout can configure eclipse by running "mvn
> >> >> -Psetup"
> >> >>> <profile>
> >> >>> <id>setup</id>
> >> >>> <build>
> >> >>> <defaultGoal>validate</defaultGoal>
> >> >>> <plugins>
> >> >>> <plugin>
> >> >>> <artifactId>maven-eclipse-plugin</artifactId>
> >> >>> <executions>
> >> >>> <execution>
> >> >>> <id>setup</id>
> >> >>> <goals>
> >> >>> <goal>eclipse</goal>
> >> >>> </goals>
> >> >>> <phase>validate</phase>
> >> >>> </execution>
> >> >>> </executions>
> >> >>> </plugin>
> >> >>>
> >> >>> I get this error :
> >> >>>
> >> >>> [INFO]
>
> >> >>> ------------------------------------------------------------------------
> >> >>> [ERROR] BUILD ERROR
> >> >>> [INFO]
>
> >> >>> ------------------------------------------------------------------------
> >> >>> [INFO] There must be a POM in the current working directory for
> the
> >> >> Eclipse
> >> >>> plugin to work.
> >> >>> [INFO]
>
> >> >>> ------------------------------------------------------------------------
> >> >>>
> >> >>> The EclispePlugin.validate() method fails on
> >> >>>
> >> >>> if ( executedProject.getFile() == null ||
> >> >>> !executedProject.getFile().exists() ) ...
> >> >>>
> >> >>> What is the distinction between "executedProject" and "project"
> from a
> >> >>> plugin point of view ?
> >> >>> This seem to have changed in maven 2.0.9.
> >> >>>
> >> >>> My use case is not really standard, but this may suggest some
> >> >> regression
> >> >>> either in maven 2.0.9 or the eclipse plugin.
> >> >>>
> >> >>> Nicolas
> >> >>>
> >> >>>
> >> >>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
> >> >>>
> >> >>>
> >> >>> > Hi,
> >> >>> >
> >> >>> > here is my +1
> >> >>> >
> >> >>> > Thanks for the fast release!
> >> >>> >
> >> >>> > Ritchie
> >> >>> >
> >> >>> > Arnaud HERITIER wrote:
> >> >>> > > Hi,
> >> >>> > >
> >> >>> > > Since the 2.5 release we did 10 days ago, we solved 3
> annoying
> >> >> issues:
> >> >>> > > * [MECLIPSE-266] - plugin applies java facet to ear
> project
> >> >>> > > * [MECLIPSE-411] - manifest property usage is only for
> ogsi
> >> >> maifests
> >> >>> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the
> artifact
> >> >> id
> >> >>> > > and not the EclipseProjectName
> >> >>> > > We also added a new feature :
> >> >>> > > * [MECLIPSE-405] - to-maven target should allow to strip
> >> >> qualifier
> >> >>> > > when creating artifacts from osgi bundles
> >> >>> > >
> >> >>> > > There are still a lot of issues left in JIRA :
> >> >>> > >
> >> >>> >
> >> >>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> >> >>> > >
> >> >>> > > Staging repo :
> >> >>> > > http://people.apache.org/~aheritier/stage/repo/
> >> >>> > >
> >> >>> > > Staging site (I'm uploading it) :
> >> >>> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> >> >>> > >
> >> >>> > > Guide to testing staged releases:
> >> >>> > >
> >> >>
> http://maven.apache.org/guides/development/guide-testing-releases.html
> >> >>> > >
> >> >>> > > Vote open for 5 days. I'll be back on wednesday to do the
> release
> >> >> if
> >> >>> > > the vote passes.
> >> >>> > >
> >> >>> > > [ ] +1
> >> >>> > > [ ] +0
> >> >>> > > [ ] -1
> >> >>> > >
> >> >>> >
> >> >>> >
> >> >>> >
> ---------------------------------------------------------------------
> >> >>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> >>> > For additional commands, e-mail: dev-help@maven.apache.org
> >> >>> >
> >> >>> >
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> ..........................................................
> >> >>
> >> >> Arnaud HERITIER
> >> >> ..........................................................
> >> >> OCTO Technology - aheritier AT octo DOT com
> >> >> www.octo.com | blog.octo.com
> >> >> ..........................................................
> >> >> ASF - aheritier AT apache DOT org
> >> >> www.apache.org | maven.apache.org
> >> >> ...........................................................
> >> >>
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> >> For additional commands, e-mail: dev-help@maven.apache.org
> >> >>
> >> >>
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Richard van Nieuwenhoven <ri...@gmx.at>.
Hi,
just created the JIRA http://jira.codehaus.org/browse/MECLIPSE-415 and
attached the patch. This problem seems to be connected to the wrongly
used executedProject parameter and maven 2.0.9.
The stage thing is that "testProject11" fails when i remove the usage of
the executedProject.
Also i am in favour to delete the code in the validate method of the
EclipsePlugin that allows to use an other directory for the settings as
the base directory. This code can only work for very very simple
projects, so we should just delete it. And make the eclipseProjectDir =
eclipse.projectDir readonly and set it to ${basedir}
Ritchie
Arnaud HERITIER wrote:
> Ok. Thx a lot. I'll fix it with the executedProject the next week.
>
> Arnaud
>
> On Fri, Mar 28, 2008 at 12:16 PM, Richard van Nieuwenhoven <ni...@cfc.at> wrote:
>> hmmm, that seems to be a relict of the old usage of the workspace
>> variable usage (that Arnaud removed). Later today i will create an jira
>> issue and a patch. (this should not be hard to find).
>>
>> Ritchie
>>
>>
>>
>> nicolas de loof wrote:
>> > Also had this issue since 2.5-SNAPSHOTs, but never took the time to report
>> > in Jira :-/
>> >
>> > Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
>> > configuration solves this, but this is only a workaround.
>> >
>> > Nicolas.
>> >
>> > 2008/3/28, Arnaud HERITIER <ah...@gmail.com>:
>> >> Hi all,
>> >>
>> >> I just discovered a bug, or an hidden feature in 2.5 :-)
>> >> Richard, I think it is related to MECLIPSE-344.
>> >>
>> >> I store my projects in a directory which isn't my eclipse workspace.
>> >> If I define the workspace attribute to be able to read its settings,
>> >> when I call eclipse:eclipse, my projects settings are written in the
>> >> workspace and not in each project's directory.
>> >> Is it what you expected ?
>> >>
>> >> Arnaud
>> >>
>> >> N.B. : I will not be able to publish a new version before my departure
>> >> this evening, thus I'll prepare a 1.5.2 just after this one if we
>> >> decide that we have to fix the plugin (what I'm thinking)
>> >>
>> >>
>> >>
>> >> On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <ni...@apache.org>
>> >> wrote:
>> >>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest
>> >> maven
>> >>> 2.0.9 RC4 :
>> >>>
>> >>> I've set a custom profile in my corporate POM to setup eclipse. It runs
>> >> the
>> >>> validate phase and attach eclipse:eclipse plugin goal to this phase.
>> >> Using
>> >>> this, a fresh SVN checkout can configure eclipse by running "mvn
>> >> -Psetup"
>> >>> <profile>
>> >>> <id>setup</id>
>> >>> <build>
>> >>> <defaultGoal>validate</defaultGoal>
>> >>> <plugins>
>> >>> <plugin>
>> >>> <artifactId>maven-eclipse-plugin</artifactId>
>> >>> <executions>
>> >>> <execution>
>> >>> <id>setup</id>
>> >>> <goals>
>> >>> <goal>eclipse</goal>
>> >>> </goals>
>> >>> <phase>validate</phase>
>> >>> </execution>
>> >>> </executions>
>> >>> </plugin>
>> >>>
>> >>> I get this error :
>> >>>
>> >>> [INFO]
>> >>> ------------------------------------------------------------------------
>> >>> [ERROR] BUILD ERROR
>> >>> [INFO]
>> >>> ------------------------------------------------------------------------
>> >>> [INFO] There must be a POM in the current working directory for the
>> >> Eclipse
>> >>> plugin to work.
>> >>> [INFO]
>> >>> ------------------------------------------------------------------------
>> >>>
>> >>> The EclispePlugin.validate() method fails on
>> >>>
>> >>> if ( executedProject.getFile() == null ||
>> >>> !executedProject.getFile().exists() ) ...
>> >>>
>> >>> What is the distinction between "executedProject" and "project" from a
>> >>> plugin point of view ?
>> >>> This seem to have changed in maven 2.0.9.
>> >>>
>> >>> My use case is not really standard, but this may suggest some
>> >> regression
>> >>> either in maven 2.0.9 or the eclipse plugin.
>> >>>
>> >>> Nicolas
>> >>>
>> >>>
>> >>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>> >>>
>> >>>
>> >>> > Hi,
>> >>> >
>> >>> > here is my +1
>> >>> >
>> >>> > Thanks for the fast release!
>> >>> >
>> >>> > Ritchie
>> >>> >
>> >>> > Arnaud HERITIER wrote:
>> >>> > > Hi,
>> >>> > >
>> >>> > > Since the 2.5 release we did 10 days ago, we solved 3 annoying
>> >> issues:
>> >>> > > * [MECLIPSE-266] - plugin applies java facet to ear project
>> >>> > > * [MECLIPSE-411] - manifest property usage is only for ogsi
>> >> maifests
>> >>> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact
>> >> id
>> >>> > > and not the EclipseProjectName
>> >>> > > We also added a new feature :
>> >>> > > * [MECLIPSE-405] - to-maven target should allow to strip
>> >> qualifier
>> >>> > > when creating artifacts from osgi bundles
>> >>> > >
>> >>> > > There are still a lot of issues left in JIRA :
>> >>> > >
>> >>> >
>> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
>> >>> > >
>> >>> > > Staging repo :
>> >>> > > http://people.apache.org/~aheritier/stage/repo/
>> >>> > >
>> >>> > > Staging site (I'm uploading it) :
>> >>> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
>> >>> > >
>> >>> > > Guide to testing staged releases:
>> >>> > >
>> >> http://maven.apache.org/guides/development/guide-testing-releases.html
>> >>> > >
>> >>> > > Vote open for 5 days. I'll be back on wednesday to do the release
>> >> if
>> >>> > > the vote passes.
>> >>> > >
>> >>> > > [ ] +1
>> >>> > > [ ] +0
>> >>> > > [ ] -1
>> >>> > >
>> >>> >
>> >>> >
>> >>> > ---------------------------------------------------------------------
>> >>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> ..........................................................
>> >>
>> >> Arnaud HERITIER
>> >> ..........................................................
>> >> OCTO Technology - aheritier AT octo DOT com
>> >> www.octo.com | blog.octo.com
>> >> ..........................................................
>> >> ASF - aheritier AT apache DOT org
>> >> www.apache.org | maven.apache.org
>> >> ...........................................................
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Ok. Thx a lot. I'll fix it with the executedProject the next week.
Arnaud
On Fri, Mar 28, 2008 at 12:16 PM, Richard van Nieuwenhoven <ni...@cfc.at> wrote:
> hmmm, that seems to be a relict of the old usage of the workspace
> variable usage (that Arnaud removed). Later today i will create an jira
> issue and a patch. (this should not be hard to find).
>
> Ritchie
>
>
>
> nicolas de loof wrote:
> > Also had this issue since 2.5-SNAPSHOTs, but never took the time to report
> > in Jira :-/
> >
> > Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
> > configuration solves this, but this is only a workaround.
> >
> > Nicolas.
> >
> > 2008/3/28, Arnaud HERITIER <ah...@gmail.com>:
> >> Hi all,
> >>
> >> I just discovered a bug, or an hidden feature in 2.5 :-)
> >> Richard, I think it is related to MECLIPSE-344.
> >>
> >> I store my projects in a directory which isn't my eclipse workspace.
> >> If I define the workspace attribute to be able to read its settings,
> >> when I call eclipse:eclipse, my projects settings are written in the
> >> workspace and not in each project's directory.
> >> Is it what you expected ?
> >>
> >> Arnaud
> >>
> >> N.B. : I will not be able to publish a new version before my departure
> >> this evening, thus I'll prepare a 1.5.2 just after this one if we
> >> decide that we have to fix the plugin (what I'm thinking)
> >>
> >>
> >>
> >> On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <ni...@apache.org>
> >> wrote:
> >>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest
> >> maven
> >>> 2.0.9 RC4 :
> >>>
> >>> I've set a custom profile in my corporate POM to setup eclipse. It runs
> >> the
> >>> validate phase and attach eclipse:eclipse plugin goal to this phase.
> >> Using
> >>> this, a fresh SVN checkout can configure eclipse by running "mvn
> >> -Psetup"
> >>> <profile>
> >>> <id>setup</id>
> >>> <build>
> >>> <defaultGoal>validate</defaultGoal>
> >>> <plugins>
> >>> <plugin>
> >>> <artifactId>maven-eclipse-plugin</artifactId>
> >>> <executions>
> >>> <execution>
> >>> <id>setup</id>
> >>> <goals>
> >>> <goal>eclipse</goal>
> >>> </goals>
> >>> <phase>validate</phase>
> >>> </execution>
> >>> </executions>
> >>> </plugin>
> >>>
> >>> I get this error :
> >>>
> >>> [INFO]
> >>> ------------------------------------------------------------------------
> >>> [ERROR] BUILD ERROR
> >>> [INFO]
> >>> ------------------------------------------------------------------------
> >>> [INFO] There must be a POM in the current working directory for the
> >> Eclipse
> >>> plugin to work.
> >>> [INFO]
> >>> ------------------------------------------------------------------------
> >>>
> >>> The EclispePlugin.validate() method fails on
> >>>
> >>> if ( executedProject.getFile() == null ||
> >>> !executedProject.getFile().exists() ) ...
> >>>
> >>> What is the distinction between "executedProject" and "project" from a
> >>> plugin point of view ?
> >>> This seem to have changed in maven 2.0.9.
> >>>
> >>> My use case is not really standard, but this may suggest some
> >> regression
> >>> either in maven 2.0.9 or the eclipse plugin.
> >>>
> >>> Nicolas
> >>>
> >>>
> >>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
> >>>
> >>>
> >>> > Hi,
> >>> >
> >>> > here is my +1
> >>> >
> >>> > Thanks for the fast release!
> >>> >
> >>> > Ritchie
> >>> >
> >>> > Arnaud HERITIER wrote:
> >>> > > Hi,
> >>> > >
> >>> > > Since the 2.5 release we did 10 days ago, we solved 3 annoying
> >> issues:
> >>> > > * [MECLIPSE-266] - plugin applies java facet to ear project
> >>> > > * [MECLIPSE-411] - manifest property usage is only for ogsi
> >> maifests
> >>> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact
> >> id
> >>> > > and not the EclipseProjectName
> >>> > > We also added a new feature :
> >>> > > * [MECLIPSE-405] - to-maven target should allow to strip
> >> qualifier
> >>> > > when creating artifacts from osgi bundles
> >>> > >
> >>> > > There are still a lot of issues left in JIRA :
> >>> > >
> >>> >
> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> >>> > >
> >>> > > Staging repo :
> >>> > > http://people.apache.org/~aheritier/stage/repo/
> >>> > >
> >>> > > Staging site (I'm uploading it) :
> >>> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> >>> > >
> >>> > > Guide to testing staged releases:
> >>> > >
> >> http://maven.apache.org/guides/development/guide-testing-releases.html
> >>> > >
> >>> > > Vote open for 5 days. I'll be back on wednesday to do the release
> >> if
> >>> > > the vote passes.
> >>> > >
> >>> > > [ ] +1
> >>> > > [ ] +0
> >>> > > [ ] -1
> >>> > >
> >>> >
> >>> >
> >>> > ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> > For additional commands, e-mail: dev-help@maven.apache.org
> >>> >
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> ..........................................................
> >>
> >> Arnaud HERITIER
> >> ..........................................................
> >> OCTO Technology - aheritier AT octo DOT com
> >> www.octo.com | blog.octo.com
> >> ..........................................................
> >> ASF - aheritier AT apache DOT org
> >> www.apache.org | maven.apache.org
> >> ...........................................................
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
hmmm, that seems to be a relict of the old usage of the workspace
variable usage (that Arnaud removed). Later today i will create an jira
issue and a patch. (this should not be hard to find).
Ritchie
nicolas de loof wrote:
> Also had this issue since 2.5-SNAPSHOTs, but never took the time to report
> in Jira :-/
>
> Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
> configuration solves this, but this is only a workaround.
>
> Nicolas.
>
> 2008/3/28, Arnaud HERITIER <ah...@gmail.com>:
>> Hi all,
>>
>> I just discovered a bug, or an hidden feature in 2.5 :-)
>> Richard, I think it is related to MECLIPSE-344.
>>
>> I store my projects in a directory which isn't my eclipse workspace.
>> If I define the workspace attribute to be able to read its settings,
>> when I call eclipse:eclipse, my projects settings are written in the
>> workspace and not in each project's directory.
>> Is it what you expected ?
>>
>> Arnaud
>>
>> N.B. : I will not be able to publish a new version before my departure
>> this evening, thus I'll prepare a 1.5.2 just after this one if we
>> decide that we have to fix the plugin (what I'm thinking)
>>
>>
>>
>> On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <ni...@apache.org>
>> wrote:
>>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest
>> maven
>>> 2.0.9 RC4 :
>>>
>>> I've set a custom profile in my corporate POM to setup eclipse. It runs
>> the
>>> validate phase and attach eclipse:eclipse plugin goal to this phase.
>> Using
>>> this, a fresh SVN checkout can configure eclipse by running "mvn
>> -Psetup"
>>> <profile>
>>> <id>setup</id>
>>> <build>
>>> <defaultGoal>validate</defaultGoal>
>>> <plugins>
>>> <plugin>
>>> <artifactId>maven-eclipse-plugin</artifactId>
>>> <executions>
>>> <execution>
>>> <id>setup</id>
>>> <goals>
>>> <goal>eclipse</goal>
>>> </goals>
>>> <phase>validate</phase>
>>> </execution>
>>> </executions>
>>> </plugin>
>>>
>>> I get this error :
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] There must be a POM in the current working directory for the
>> Eclipse
>>> plugin to work.
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> The EclispePlugin.validate() method fails on
>>>
>>> if ( executedProject.getFile() == null ||
>>> !executedProject.getFile().exists() ) ...
>>>
>>> What is the distinction between "executedProject" and "project" from a
>>> plugin point of view ?
>>> This seem to have changed in maven 2.0.9.
>>>
>>> My use case is not really standard, but this may suggest some
>> regression
>>> either in maven 2.0.9 or the eclipse plugin.
>>>
>>> Nicolas
>>>
>>>
>>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>>>
>>>
>>> > Hi,
>>> >
>>> > here is my +1
>>> >
>>> > Thanks for the fast release!
>>> >
>>> > Ritchie
>>> >
>>> > Arnaud HERITIER wrote:
>>> > > Hi,
>>> > >
>>> > > Since the 2.5 release we did 10 days ago, we solved 3 annoying
>> issues:
>>> > > * [MECLIPSE-266] - plugin applies java facet to ear project
>>> > > * [MECLIPSE-411] - manifest property usage is only for ogsi
>> maifests
>>> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact
>> id
>>> > > and not the EclipseProjectName
>>> > > We also added a new feature :
>>> > > * [MECLIPSE-405] - to-maven target should allow to strip
>> qualifier
>>> > > when creating artifacts from osgi bundles
>>> > >
>>> > > There are still a lot of issues left in JIRA :
>>> > >
>>> >
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
>>> > >
>>> > > Staging repo :
>>> > > http://people.apache.org/~aheritier/stage/repo/
>>> > >
>>> > > Staging site (I'm uploading it) :
>>> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
>>> > >
>>> > > Guide to testing staged releases:
>>> > >
>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>> > >
>>> > > Vote open for 5 days. I'll be back on wednesday to do the release
>> if
>>> > > the vote passes.
>>> > >
>>> > > [ ] +1
>>> > > [ ] +0
>>> > > [ ] -1
>>> > >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> > For additional commands, e-mail: dev-help@maven.apache.org
>>> >
>>> >
>>>
>>
>>
>>
>> --
>> ..........................................................
>>
>> Arnaud HERITIER
>> ..........................................................
>> OCTO Technology - aheritier AT octo DOT com
>> www.octo.com | blog.octo.com
>> ..........................................................
>> ASF - aheritier AT apache DOT org
>> www.apache.org | maven.apache.org
>> ...........................................................
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by nicolas de loof <ni...@apache.org>.
Also had this issue since 2.5-SNAPSHOTs, but never took the time to report
in Jira :-/
Setting eclipse.projectDir=${basedir} in the POM eclipse-plugin
configuration solves this, but this is only a workaround.
Nicolas.
2008/3/28, Arnaud HERITIER <ah...@gmail.com>:
>
> Hi all,
>
> I just discovered a bug, or an hidden feature in 2.5 :-)
> Richard, I think it is related to MECLIPSE-344.
>
> I store my projects in a directory which isn't my eclipse workspace.
> If I define the workspace attribute to be able to read its settings,
> when I call eclipse:eclipse, my projects settings are written in the
> workspace and not in each project's directory.
> Is it what you expected ?
>
> Arnaud
>
> N.B. : I will not be able to publish a new version before my departure
> this evening, thus I'll prepare a 1.5.2 just after this one if we
> decide that we have to fix the plugin (what I'm thinking)
>
>
>
> On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <ni...@apache.org>
> wrote:
> > I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest
> maven
> > 2.0.9 RC4 :
> >
> > I've set a custom profile in my corporate POM to setup eclipse. It runs
> the
> > validate phase and attach eclipse:eclipse plugin goal to this phase.
> Using
> > this, a fresh SVN checkout can configure eclipse by running "mvn
> -Psetup"
> >
> > <profile>
> > <id>setup</id>
> > <build>
> > <defaultGoal>validate</defaultGoal>
> > <plugins>
> > <plugin>
> > <artifactId>maven-eclipse-plugin</artifactId>
> > <executions>
> > <execution>
> > <id>setup</id>
> > <goals>
> > <goal>eclipse</goal>
> > </goals>
> > <phase>validate</phase>
> > </execution>
> > </executions>
> > </plugin>
> >
> > I get this error :
> >
> > [INFO]
>
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
>
> > ------------------------------------------------------------------------
> > [INFO] There must be a POM in the current working directory for the
> Eclipse
> > plugin to work.
> > [INFO]
>
> > ------------------------------------------------------------------------
> >
> > The EclispePlugin.validate() method fails on
> >
> > if ( executedProject.getFile() == null ||
> > !executedProject.getFile().exists() ) ...
> >
> > What is the distinction between "executedProject" and "project" from a
> > plugin point of view ?
> > This seem to have changed in maven 2.0.9.
> >
> > My use case is not really standard, but this may suggest some
> regression
> > either in maven 2.0.9 or the eclipse plugin.
> >
> > Nicolas
> >
> >
> > 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
> >
> >
> > >
> > > Hi,
> > >
> > > here is my +1
> > >
> > > Thanks for the fast release!
> > >
> > > Ritchie
> > >
> > > Arnaud HERITIER wrote:
> > > > Hi,
> > > >
> > > > Since the 2.5 release we did 10 days ago, we solved 3 annoying
> issues:
> > > > * [MECLIPSE-266] - plugin applies java facet to ear project
> > > > * [MECLIPSE-411] - manifest property usage is only for ogsi
> maifests
> > > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact
> id
> > > > and not the EclipseProjectName
> > > > We also added a new feature :
> > > > * [MECLIPSE-405] - to-maven target should allow to strip
> qualifier
> > > > when creating artifacts from osgi bundles
> > > >
> > > > There are still a lot of issues left in JIRA :
> > > >
> > >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> > > >
> > > > Staging repo :
> > > > http://people.apache.org/~aheritier/stage/repo/
> > > >
> > > > Staging site (I'm uploading it) :
> > > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> > > >
> > > > Guide to testing staged releases:
> > > >
> http://maven.apache.org/guides/development/guide-testing-releases.html
> > > >
> > > > Vote open for 5 days. I'll be back on wednesday to do the release
> if
> > > > the vote passes.
> > > >
> > > > [ ] +1
> > > > [ ] +0
> > > > [ ] -1
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
>
>
>
>
> --
> ..........................................................
>
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi all,
I just discovered a bug, or an hidden feature in 2.5 :-)
Richard, I think it is related to MECLIPSE-344.
I store my projects in a directory which isn't my eclipse workspace.
If I define the workspace attribute to be able to read its settings,
when I call eclipse:eclipse, my projects settings are written in the
workspace and not in each project's directory.
Is it what you expected ?
Arnaud
N.B. : I will not be able to publish a new version before my departure
this evening, thus I'll prepare a 1.5.2 just after this one if we
decide that we have to fix the plugin (what I'm thinking)
On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <ni...@apache.org> wrote:
> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest maven
> 2.0.9 RC4 :
>
> I've set a custom profile in my corporate POM to setup eclipse. It runs the
> validate phase and attach eclipse:eclipse plugin goal to this phase. Using
> this, a fresh SVN checkout can configure eclipse by running "mvn -Psetup"
>
> <profile>
> <id>setup</id>
> <build>
> <defaultGoal>validate</defaultGoal>
> <plugins>
> <plugin>
> <artifactId>maven-eclipse-plugin</artifactId>
> <executions>
> <execution>
> <id>setup</id>
> <goals>
> <goal>eclipse</goal>
> </goals>
> <phase>validate</phase>
> </execution>
> </executions>
> </plugin>
>
> I get this error :
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There must be a POM in the current working directory for the Eclipse
> plugin to work.
> [INFO]
> ------------------------------------------------------------------------
>
> The EclispePlugin.validate() method fails on
>
> if ( executedProject.getFile() == null ||
> !executedProject.getFile().exists() ) ...
>
> What is the distinction between "executedProject" and "project" from a
> plugin point of view ?
> This seem to have changed in maven 2.0.9.
>
> My use case is not really standard, but this may suggest some regression
> either in maven 2.0.9 or the eclipse plugin.
>
> Nicolas
>
>
> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>
>
> >
> > Hi,
> >
> > here is my +1
> >
> > Thanks for the fast release!
> >
> > Ritchie
> >
> > Arnaud HERITIER wrote:
> > > Hi,
> > >
> > > Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> > > * [MECLIPSE-266] - plugin applies java facet to ear project
> > > * [MECLIPSE-411] - manifest property usage is only for ogsi maifests
> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> > > and not the EclipseProjectName
> > > We also added a new feature :
> > > * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> > > when creating artifacts from osgi bundles
> > >
> > > There are still a lot of issues left in JIRA :
> > >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> > >
> > > Staging repo :
> > > http://people.apache.org/~aheritier/stage/repo/
> > >
> > > Staging site (I'm uploading it) :
> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> > >
> > > Guide to testing staged releases:
> > > http://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for 5 days. I'll be back on wednesday to do the release if
> > > the vote passes.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
On Fri, Mar 28, 2008 at 10:09 AM, nicolas de loof <ni...@apache.org> wrote:
> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest maven
> 2.0.9 RC4 :
>
> I've set a custom profile in my corporate POM to setup eclipse. It runs the
> validate phase and attach eclipse:eclipse plugin goal to this phase. Using
> this, a fresh SVN checkout can configure eclipse by running "mvn -Psetup"
>
> <profile>
> <id>setup</id>
> <build>
> <defaultGoal>validate</defaultGoal>
> <plugins>
> <plugin>
> <artifactId>maven-eclipse-plugin</artifactId>
> <executions>
> <execution>
> <id>setup</id>
> <goals>
> <goal>eclipse</goal>
> </goals>
> <phase>validate</phase>
> </execution>
> </executions>
> </plugin>
>
> I get this error :
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There must be a POM in the current working directory for the Eclipse
> plugin to work.
> [INFO]
> ------------------------------------------------------------------------
>
> The EclispePlugin.validate() method fails on
>
> if ( executedProject.getFile() == null ||
> !executedProject.getFile().exists() ) ...
>
> What is the distinction between "executedProject" and "project" from a
> plugin point of view ?
> This seem to have changed in maven 2.0.9.
I never understood thus I didn't touch it ;-)
>
> My use case is not really standard, but this may suggest some regression
> either in maven 2.0.9 or the eclipse plugin.
I didn't test the RC4 but there's probably something to fix in it. I'm
not sure that we are the only plugin to use this.
If someone can explain what the difference is, it can help us to
remove it, because I think it creates a lot of issues (sometime
project is used, and sometime it is executedProjet without any logic)
Arnaud
>
> Nicolas
>
>
> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>
>
> >
> > Hi,
> >
> > here is my +1
> >
> > Thanks for the fast release!
> >
> > Ritchie
> >
> > Arnaud HERITIER wrote:
> > > Hi,
> > >
> > > Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> > > * [MECLIPSE-266] - plugin applies java facet to ear project
> > > * [MECLIPSE-411] - manifest property usage is only for ogsi maifests
> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> > > and not the EclipseProjectName
> > > We also added a new feature :
> > > * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> > > when creating artifacts from osgi bundles
> > >
> > > There are still a lot of issues left in JIRA :
> > >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> > >
> > > Staging repo :
> > > http://people.apache.org/~aheritier/stage/repo/
> > >
> > > Staging site (I'm uploading it) :
> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> > >
> > > Guide to testing staged releases:
> > > http://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for 5 days. I'll be back on wednesday to do the release if
> > > the vote passes.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by John Casey <jd...@commonjava.org>.
I think I've found a fix for the issue in the 2.0.9 code. I've
committed it along with two new integration tests under the issue
MNG-3221. Hopefully there will be a new RC soon that you can check
against.
Thanks,
-john
On Mar 28, 2008, at 6:06 AM, nicolas de loof wrote:
> I found the cause of this issue :
>
> As I added the SysdeoMojo.generate execution to this setup profile,
> two
> plugins (eclipse + sysdeo-tomcat) request for a forked @execute
> phase="generate-resources".
>
> In both case, maven remove the requesting plugin from the forked
> lifecycle
> to prevent recursive calls, but ONLY the requesting plugin is
> removed (not
> all the plugins that request such a fork). So I get :
>
> mvn -Psetup
> "validate" phase
> |_ eclipse:eclipse Fork @execute phase="generate-resources"
> "validate" phase
> |_ sysdeo:tomcat
> "generate-resources" phase
> |_ ...
> eclipse:eclipse execute()
> |_ sysdeo:tomcat Fork @execute phase="generate-resources"
> "validate" phase
> |_ eclipse:eclipse // FAILS as there is no
> executedProject.getFile()
> ???
>
>
> A workaround is that the sysdeo:tomcat plugin that DOES NOT require
> a forked
> execution (executedProject is never read).
>
> Why does the eclipse plugin require the executedProject ? As this
> is not an
> @aggregator Mojo, the ${project}.getBaseDir() will allways reflect the
> current project directory AFAIK ?
>
>
> I'm not sure if my use case is valid, but it is really usefull for
> maven
> adoption here, as this makes setup really simplier. I've discovered
> this way
> to use profiles as maven "macros" from the CXF project.
>
> Nicolas.
>
>
> 2008/3/28, nicolas de loof <ni...@apache.org>:
>>
>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with
>> latest
>> maven 2.0.9 RC4 :
>>
>> I've set a custom profile in my corporate POM to setup eclipse. It
>> runs
>> the validate phase and attach eclipse:eclipse plugin goal to this
>> phase.
>> Using this, a fresh SVN checkout can configure eclipse by running
>> "mvn
>> -Psetup"
>>
>> <profile>
>> <id>setup</id>
>> <build>
>> <defaultGoal>validate</defaultGoal>
>> <plugins>
>> <plugin>
>> <artifactId>maven-eclipse-plugin</artifactId>
>> <executions>
>> <execution>
>> <id>setup</id>
>> <goals>
>> <goal>eclipse</goal>
>> </goals>
>> <phase>validate</phase>
>> </execution>
>> </executions>
>> </plugin>
>>
>> I get this error :
>>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] There must be a POM in the current working directory for the
>> Eclipse plugin to work.
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>>
>> The EclispePlugin.validate() method fails on
>>
>> if ( executedProject.getFile() == null ||
>> !executedProject.getFile().exists() ) ...
>>
>> What is the distinction between "executedProject" and "project"
>> from a
>> plugin point of view ?
>> This seem to have changed in maven 2.0.9.
>>
>> My use case is not really standard, but this may suggest some
>> regression
>> either in maven 2.0.9 or the eclipse plugin.
>>
>> Nicolas
>>
>>
>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>>>
>>> Hi,
>>>
>>> here is my +1
>>>
>>> Thanks for the fast release!
>>>
>>> Ritchie
>>>
>>> Arnaud HERITIER wrote:
>>>> Hi,
>>>>
>>>> Since the 2.5 release we did 10 days ago, we solved 3 annoying
>>> issues:
>>>> * [MECLIPSE-266] - plugin applies java facet to ear project
>>>> * [MECLIPSE-411] - manifest property usage is only for ogsi
>>> maifests
>>>> * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the
>>>> artifact id
>>>> and not the EclipseProjectName
>>>> We also added a new feature :
>>>> * [MECLIPSE-405] - to-maven target should allow to strip
>>>> qualifier
>>>> when creating artifacts from osgi bundles
>>>>
>>>> There are still a lot of issues left in JIRA :
>>>>
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa?
>>> reset=true&pid=11133&status=1
>>>>
>>>> Staging repo :
>>>> http://people.apache.org/~aheritier/stage/repo/<http://
>>>> people.apache.org/%7Eaheritier/stage/repo/>
>>>>
>>>> Staging site (I'm uploading it) :
>>>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
>>>>
>>>> Guide to testing staged releases:
>>>> http://maven.apache.org/guides/development/guide-testing-
>>>> releases.html
>>>>
>>>> Vote open for 5 days. I'll be back on wednesday to do the
>>>> release if
>>>> the vote passes.
>>>>
>>>> [ ] +1
>>>> [ ] +0
>>>> [ ] -1
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Stuart McCulloch <st...@jayway.net>.
On 28/03/2008, nicolas de loof <ni...@apache.org> wrote:
>
> I found the cause of this issue :
>
> As I added the SysdeoMojo.generate execution to this setup profile, two
> plugins (eclipse + sysdeo-tomcat) request for a forked @execute
> phase="generate-resources".
>
> In both case, maven remove the requesting plugin from the forked lifecycle
> to prevent recursive calls, but ONLY the requesting plugin is removed (not
> all the plugins that request such a fork). So I get :
>
> mvn -Psetup
> "validate" phase
> |_ eclipse:eclipse Fork @execute phase="generate-resources"
> "validate" phase
> |_ sysdeo:tomcat
> "generate-resources" phase
> |_ ...
> eclipse:eclipse execute()
> |_ sysdeo:tomcat Fork @execute phase="generate-resources"
> "validate" phase
> |_ eclipse:eclipse // FAILS as there is no
> executedProject.getFile()
> ???
>
>
> A workaround is that the sysdeo:tomcat plugin that DOES NOT require a
> forked
> execution (executedProject is never read).
>
> Why does the eclipse plugin require the executedProject ? As this is not
> an
> @aggregator Mojo, the ${project}.getBaseDir() will allways reflect the
> current project directory AFAIK ?
according to the mojo docs:
http://maven.apache.org/developers/mojo-api-specification.html
@execute will fork a parallel lifecycle, and in a multi-module project
this could mean that ${executedProject} is one of the "leaf" modules,
while ${project} is the project where the lifecycle was forked
so if you just use ${project} with @execute you could find it points
to the parent project, not the project you actually want to process
... if that makes sense :)
I'm not sure if my use case is valid, but it is really usefull for maven
> adoption here, as this makes setup really simplier. I've discovered this
> way
> to use profiles as maven "macros" from the CXF project.
>
> Nicolas.
>
>
> 2008/3/28, nicolas de loof <ni...@apache.org>:
>
> >
> > I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest
> > maven 2.0.9 RC4 :
> >
> > I've set a custom profile in my corporate POM to setup eclipse. It runs
> > the validate phase and attach eclipse:eclipse plugin goal to this phase.
> > Using this, a fresh SVN checkout can configure eclipse by running "mvn
> > -Psetup"
> >
> > <profile>
> > <id>setup</id>
> > <build>
> > <defaultGoal>validate</defaultGoal>
> > <plugins>
> > <plugin>
> > <artifactId>maven-eclipse-plugin</artifactId>
> > <executions>
> > <execution>
> > <id>setup</id>
> > <goals>
> > <goal>eclipse</goal>
> > </goals>
> > <phase>validate</phase>
> > </execution>
> > </executions>
> > </plugin>
> >
> > I get this error :
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] There must be a POM in the current working directory for the
> > Eclipse plugin to work.
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > The EclispePlugin.validate() method fails on
> >
> > if ( executedProject.getFile() == null ||
> > !executedProject.getFile().exists() ) ...
> >
> > What is the distinction between "executedProject" and "project" from a
> > plugin point of view ?
> > This seem to have changed in maven 2.0.9.
> >
> > My use case is not really standard, but this may suggest some regression
> > either in maven 2.0.9 or the eclipse plugin.
> >
> > Nicolas
> >
> >
> > 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
> > >
> > > Hi,
> > >
> > > here is my +1
> > >
> > > Thanks for the fast release!
> > >
> > > Ritchie
> > >
> > > Arnaud HERITIER wrote:
> > > > Hi,
> > > >
> > > > Since the 2.5 release we did 10 days ago, we solved 3 annoying
> > > issues:
> > > > * [MECLIPSE-266] - plugin applies java facet to ear project
> > > > * [MECLIPSE-411] - manifest property usage is only for ogsi
> > > maifests
> > > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact
> id
> > > > and not the EclipseProjectName
> > > > We also added a new feature :
> > > > * [MECLIPSE-405] - to-maven target should allow to strip
> qualifier
> > > > when creating artifacts from osgi bundles
> > > >
> > > > There are still a lot of issues left in JIRA :
> > > >
> > >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> > > >
> > > > Staging repo :
>
> > > > http://people.apache.org/~aheritier/stage/repo/<
> http://people.apache.org/%7Eaheritier/stage/repo/>
>
> > > >
> > > > Staging site (I'm uploading it) :
> > > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> > > >
> > > > Guide to testing staged releases:
> > > >
> http://maven.apache.org/guides/development/guide-testing-releases.html
> > > >
> > > > Vote open for 5 days. I'll be back on wednesday to do the release if
> > > > the vote passes.
> > > >
> > > > [ ] +1
> > > > [ ] +0
> > > > [ ] -1
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
>
--
Cheers, Stuart
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by John Casey <jd...@commonjava.org>.
I think the issue probably has something to do with the fix I added
to maven-core for MNG-3221. I'm looking into that code now to see if
I can figure out how the modification breaks this case.
-john
On Mar 28, 2008, at 6:06 AM, nicolas de loof wrote:
> I found the cause of this issue :
>
> As I added the SysdeoMojo.generate execution to this setup profile,
> two
> plugins (eclipse + sysdeo-tomcat) request for a forked @execute
> phase="generate-resources".
>
> In both case, maven remove the requesting plugin from the forked
> lifecycle
> to prevent recursive calls, but ONLY the requesting plugin is
> removed (not
> all the plugins that request such a fork). So I get :
>
> mvn -Psetup
> "validate" phase
> |_ eclipse:eclipse Fork @execute phase="generate-resources"
> "validate" phase
> |_ sysdeo:tomcat
> "generate-resources" phase
> |_ ...
> eclipse:eclipse execute()
> |_ sysdeo:tomcat Fork @execute phase="generate-resources"
> "validate" phase
> |_ eclipse:eclipse // FAILS as there is no
> executedProject.getFile()
> ???
>
>
> A workaround is that the sysdeo:tomcat plugin that DOES NOT require
> a forked
> execution (executedProject is never read).
>
> Why does the eclipse plugin require the executedProject ? As this
> is not an
> @aggregator Mojo, the ${project}.getBaseDir() will allways reflect the
> current project directory AFAIK ?
>
>
> I'm not sure if my use case is valid, but it is really usefull for
> maven
> adoption here, as this makes setup really simplier. I've discovered
> this way
> to use profiles as maven "macros" from the CXF project.
>
> Nicolas.
>
>
> 2008/3/28, nicolas de loof <ni...@apache.org>:
>>
>> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with
>> latest
>> maven 2.0.9 RC4 :
>>
>> I've set a custom profile in my corporate POM to setup eclipse. It
>> runs
>> the validate phase and attach eclipse:eclipse plugin goal to this
>> phase.
>> Using this, a fresh SVN checkout can configure eclipse by running
>> "mvn
>> -Psetup"
>>
>> <profile>
>> <id>setup</id>
>> <build>
>> <defaultGoal>validate</defaultGoal>
>> <plugins>
>> <plugin>
>> <artifactId>maven-eclipse-plugin</artifactId>
>> <executions>
>> <execution>
>> <id>setup</id>
>> <goals>
>> <goal>eclipse</goal>
>> </goals>
>> <phase>validate</phase>
>> </execution>
>> </executions>
>> </plugin>
>>
>> I get this error :
>>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] There must be a POM in the current working directory for the
>> Eclipse plugin to work.
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>>
>> The EclispePlugin.validate() method fails on
>>
>> if ( executedProject.getFile() == null ||
>> !executedProject.getFile().exists() ) ...
>>
>> What is the distinction between "executedProject" and "project"
>> from a
>> plugin point of view ?
>> This seem to have changed in maven 2.0.9.
>>
>> My use case is not really standard, but this may suggest some
>> regression
>> either in maven 2.0.9 or the eclipse plugin.
>>
>> Nicolas
>>
>>
>> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>>>
>>> Hi,
>>>
>>> here is my +1
>>>
>>> Thanks for the fast release!
>>>
>>> Ritchie
>>>
>>> Arnaud HERITIER wrote:
>>>> Hi,
>>>>
>>>> Since the 2.5 release we did 10 days ago, we solved 3 annoying
>>> issues:
>>>> * [MECLIPSE-266] - plugin applies java facet to ear project
>>>> * [MECLIPSE-411] - manifest property usage is only for ogsi
>>> maifests
>>>> * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the
>>>> artifact id
>>>> and not the EclipseProjectName
>>>> We also added a new feature :
>>>> * [MECLIPSE-405] - to-maven target should allow to strip
>>>> qualifier
>>>> when creating artifacts from osgi bundles
>>>>
>>>> There are still a lot of issues left in JIRA :
>>>>
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa?
>>> reset=true&pid=11133&status=1
>>>>
>>>> Staging repo :
>>>> http://people.apache.org/~aheritier/stage/repo/<http://
>>>> people.apache.org/%7Eaheritier/stage/repo/>
>>>>
>>>> Staging site (I'm uploading it) :
>>>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
>>>>
>>>> Guide to testing staged releases:
>>>> http://maven.apache.org/guides/development/guide-testing-
>>>> releases.html
>>>>
>>>> Vote open for 5 days. I'll be back on wednesday to do the
>>>> release if
>>>> the vote passes.
>>>>
>>>> [ ] +1
>>>> [ ] +0
>>>> [ ] -1
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by nicolas de loof <ni...@apache.org>.
I found the cause of this issue :
As I added the SysdeoMojo.generate execution to this setup profile, two
plugins (eclipse + sysdeo-tomcat) request for a forked @execute
phase="generate-resources".
In both case, maven remove the requesting plugin from the forked lifecycle
to prevent recursive calls, but ONLY the requesting plugin is removed (not
all the plugins that request such a fork). So I get :
mvn -Psetup
"validate" phase
|_ eclipse:eclipse Fork @execute phase="generate-resources"
"validate" phase
|_ sysdeo:tomcat
"generate-resources" phase
|_ ...
eclipse:eclipse execute()
|_ sysdeo:tomcat Fork @execute phase="generate-resources"
"validate" phase
|_ eclipse:eclipse // FAILS as there is no executedProject.getFile()
???
A workaround is that the sysdeo:tomcat plugin that DOES NOT require a forked
execution (executedProject is never read).
Why does the eclipse plugin require the executedProject ? As this is not an
@aggregator Mojo, the ${project}.getBaseDir() will allways reflect the
current project directory AFAIK ?
I'm not sure if my use case is valid, but it is really usefull for maven
adoption here, as this makes setup really simplier. I've discovered this way
to use profiles as maven "macros" from the CXF project.
Nicolas.
2008/3/28, nicolas de loof <ni...@apache.org>:
>
> I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest
> maven 2.0.9 RC4 :
>
> I've set a custom profile in my corporate POM to setup eclipse. It runs
> the validate phase and attach eclipse:eclipse plugin goal to this phase.
> Using this, a fresh SVN checkout can configure eclipse by running "mvn
> -Psetup"
>
> <profile>
> <id>setup</id>
> <build>
> <defaultGoal>validate</defaultGoal>
> <plugins>
> <plugin>
> <artifactId>maven-eclipse-plugin</artifactId>
> <executions>
> <execution>
> <id>setup</id>
> <goals>
> <goal>eclipse</goal>
> </goals>
> <phase>validate</phase>
> </execution>
> </executions>
> </plugin>
>
> I get this error :
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There must be a POM in the current working directory for the
> Eclipse plugin to work.
> [INFO]
> ------------------------------------------------------------------------
>
> The EclispePlugin.validate() method fails on
>
> if ( executedProject.getFile() == null ||
> !executedProject.getFile().exists() ) ...
>
> What is the distinction between "executedProject" and "project" from a
> plugin point of view ?
> This seem to have changed in maven 2.0.9.
>
> My use case is not really standard, but this may suggest some regression
> either in maven 2.0.9 or the eclipse plugin.
>
> Nicolas
>
>
> 2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
> >
> > Hi,
> >
> > here is my +1
> >
> > Thanks for the fast release!
> >
> > Ritchie
> >
> > Arnaud HERITIER wrote:
> > > Hi,
> > >
> > > Since the 2.5 release we did 10 days ago, we solved 3 annoying
> > issues:
> > > * [MECLIPSE-266] - plugin applies java facet to ear project
> > > * [MECLIPSE-411] - manifest property usage is only for ogsi
> > maifests
> > > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> > > and not the EclipseProjectName
> > > We also added a new feature :
> > > * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> > > when creating artifacts from osgi bundles
> > >
> > > There are still a lot of issues left in JIRA :
> > >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> > >
> > > Staging repo :
> > > http://people.apache.org/~aheritier/stage/repo/<http://people.apache.org/%7Eaheritier/stage/repo/>
> > >
> > > Staging site (I'm uploading it) :
> > > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> > >
> > > Guide to testing staged releases:
> > > http://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > Vote open for 5 days. I'll be back on wednesday to do the release if
> > > the vote passes.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by nicolas de loof <ni...@apache.org>.
I've got an issue with eclipse plugin 2.5 & 2.5.1 combined with latest maven
2.0.9 RC4 :
I've set a custom profile in my corporate POM to setup eclipse. It runs the
validate phase and attach eclipse:eclipse plugin goal to this phase. Using
this, a fresh SVN checkout can configure eclipse by running "mvn -Psetup"
<profile>
<id>setup</id>
<build>
<defaultGoal>validate</defaultGoal>
<plugins>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<executions>
<execution>
<id>setup</id>
<goals>
<goal>eclipse</goal>
</goals>
<phase>validate</phase>
</execution>
</executions>
</plugin>
I get this error :
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] There must be a POM in the current working directory for the Eclipse
plugin to work.
[INFO]
------------------------------------------------------------------------
The EclispePlugin.validate() method fails on
if ( executedProject.getFile() == null ||
!executedProject.getFile().exists() ) ...
What is the distinction between "executedProject" and "project" from a
plugin point of view ?
This seem to have changed in maven 2.0.9.
My use case is not really standard, but this may suggest some regression
either in maven 2.0.9 or the eclipse plugin.
Nicolas
2008/3/28, Richard van Nieuwenhoven <ni...@cfc.at>:
>
> Hi,
>
> here is my +1
>
> Thanks for the fast release!
>
> Ritchie
>
> Arnaud HERITIER wrote:
> > Hi,
> >
> > Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> > * [MECLIPSE-266] - plugin applies java facet to ear project
> > * [MECLIPSE-411] - manifest property usage is only for ogsi maifests
> > * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> > and not the EclipseProjectName
> > We also added a new feature :
> > * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> > when creating artifacts from osgi bundles
> >
> > There are still a lot of issues left in JIRA :
> >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
> >
> > Staging repo :
> > http://people.apache.org/~aheritier/stage/repo/
> >
> > Staging site (I'm uploading it) :
> > http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 5 days. I'll be back on wednesday to do the release if
> > the vote passes.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] Release Maven Eclipse plugin version 2.5.1
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
Hi,
here is my +1
Thanks for the fast release!
Ritchie
Arnaud HERITIER wrote:
> Hi,
>
> Since the 2.5 release we did 10 days ago, we solved 3 annoying issues:
> * [MECLIPSE-266] - plugin applies java facet to ear project
> * [MECLIPSE-411] - manifest property usage is only for ogsi maifests
> * [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
> and not the EclipseProjectName
> We also added a new feature :
> * [MECLIPSE-405] - to-maven target should allow to strip qualifier
> when creating artifacts from osgi bundles
>
> There are still a lot of issues left in JIRA :
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&status=1
>
> Staging repo :
> http://people.apache.org/~aheritier/stage/repo/
>
> Staging site (I'm uploading it) :
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.5.1/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 5 days. I'll be back on wednesday to do the release if
> the vote passes.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org