You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2007/07/04 21:39:18 UTC
[VOTE] maven-eclipse-plugin 2.4
It's been about 5 months since an eclipse plugin release and we have
lots of fixes and a handful of enhancements:
Bug
* [MECLIPSE-108] - .wtpmodules with version 2.4 for
javax.servlet:servlet-api:2.3
* [MECLIPSE-109] - .component wb-resource source path incorrect for ear
packaging
* [MECLIPSE-151] - Incorrect name for test sources jars
* [MECLIPSE-198] - EJB version is not resloved
* [MECLIPSE-215] - WTP 1.5 Documentation
* [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
eclipse:eclipse for war and ejb projects.
* [MECLIPSE-225] - Invalid .classpath Entries.
* [MECLIPSE-233] - Manifest attributes incorrectly treated as
case-sensitive
* [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
String method argument causing maven-eclipse.xml copy-resources problems
* [MECLIPSE-236] - eclipse:make-artifacts should preserve the
resolution:=optional directive
* [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
* [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
wtp facet
* [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
to be built
* [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
* [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
in pom.xml
* [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
Java 5.0 project
* [MECLIPSE-278] - duplicated classpathentries
* [MECLIPSE-279] - PDE projects should be considered java projects in
all cases
* [MECLIPSE-287] - Regression - fails to correctly construct classpath
containing dependencies with classifiers
Improvement
* [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
* [MECLIPSE-267] - Resolve version ranges in make-artifacts
* [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
version, jsp version, ... possible through pom configuration
* [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
creation while executing eclipse:rad
New Feature
* [MECLIPSE-119] - Allow custom project name for eclipse projects
* [MECLIPSE-189] - addVersionToProjectName property
* [MECLIPSE-251] - Allows prefixing of eclipse project name
* [MECLIPSE-271] - Ability to skip
The site has been updated:
http://maven.apache.org/plugins/maven-eclipse-plugin
Plugin is staged here:
http://people.apache.org/~brianf/staging-repository/
Vote is open for 72hrs.
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Arnaud HERITIER <ah...@gmail.com>.
ok, thus the vote continue ?
Build problems are solved ?
Arnaud
On 05/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Same thing with this one, the patch doesn't exist yet along with tests
> or doc changes. If we have to respin the release because of the test
> problems, then we can grab a few patches if they are complete, otherwise
> I say they wait. We've been discussing releasing for several weeks now
> and need to pull the trigger at some point. We shouldn't wait another 5
> months before releasing again so this doesn't become a problem.
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: Thursday, July 05, 2007 4:55 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> We just received a comment about MECLIPSE-184 (it was in private
> before).
> WDYT ? I'm not a ear user...
>
> Arnaud
>
>
> On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > It's been about 5 months since an eclipse plugin release and we have
> > lots of fixes and a handful of enhancements:
> >
> > Bug
> > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > javax.servlet:servlet-api:2.3
> > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> ear
> > packaging
> > * [MECLIPSE-151] - Incorrect name for test sources jars
> > * [MECLIPSE-198] - EJB version is not resloved
> > * [MECLIPSE-215] - WTP 1.5 Documentation
> > * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> > eclipse:eclipse for war and ejb projects.
> > * [MECLIPSE-225] - Invalid .classpath Entries.
> > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > case-sensitive
> > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> > String method argument causing maven-eclipse.xml copy-resources
> problems
> > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > resolution:=optional directive
> > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
> in
> > wtp facet
> > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> Server
> > to be built
> > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> defined
> > in pom.xml
> > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> > Java 5.0 project
> > * [MECLIPSE-278] - duplicated classpathentries
> > * [MECLIPSE-279] - PDE projects should be considered java projects in
> > all cases
> > * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> > containing dependencies with classifiers
> > Improvement
> > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> > version, jsp version, ... possible through pom configuration
> > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> > creation while executing eclipse:rad
> > New Feature
> > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> > * [MECLIPSE-189] - addVersionToProjectName property
> > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > * [MECLIPSE-271] - Ability to skip
> >
> > The site has been updated:
> > http://maven.apache.org/plugins/maven-eclipse-plugin
> >
> > Plugin is staged here:
> > http://people.apache.org/~brianf/staging-repository/
> >
> > Vote is open for 72hrs.
> >
> > +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@octo.com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier@apache.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@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Graham Leggett <mi...@sharp.fm>.
On Thu, July 5, 2007 3:23 pm, Brian E. Fox wrote:
> It's a recurring cycle where we wait and wait and before you know
> it, it's 5 months like it is now with good functionality already sitting
> there.
+1.
Release early, release often.
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Arnaud HERITIER <ah...@gmail.com>.
+1. Tested with eclipse 2.2 and wtp 1.5.x for wars
I saw an issue about wtp 2.x support. I just upgraded to eclipse 3.3.
We'll plan the support for it in 2.5 (it can be out quicly if we have
some help !!).
Arnaud
On 05/07/07, Max Bowsher <ma...@ukf.net> wrote:
> Richard van Nieuwenhoven wrote:
> > Another question did anyone test the plugin with eclipse 3.3 (with and
> > without WTP) ?
>
> Works fine on ordinary projects. I don't use WTP so I can't test that.
>
> Max.
>
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Max Bowsher <ma...@ukf.net>.
Richard van Nieuwenhoven wrote:
> Another question did anyone test the plugin with eclipse 3.3 (with and
> without WTP) ?
Works fine on ordinary projects. I don't use WTP so I can't test that.
Max.
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
ok, after this release i will make/take time for myself to create a new
patch that includes all patches of the 3 companies i know that use
patched versions.
This time i will make the time to include tests and documentation!!!
(maybe release 2.5 is not so far away)
Another question did anyone test the plugin with eclipse 3.3 (with and
without WTP) ?
Ritchie
Brian E. Fox wrote:
> Ritchie,
> I understand the issue but on the flip side, without tests to ensure the
> functionality works as expected, we can't verify it. I don't personally
> use this functionality of the plugin so I can't tell at a glance if it's
> right or not. As I see it, once we are this close to a release
> (discussion about preparing for it occurred mid-june) then only complete
> patches can be considered for inclusion. Otherwise we might have to wait
> another week or two until someone has time to analyze and complete the
> patch. It's a recurring cycle where we wait and wait and before you know
> it, it's 5 months like it is now with good functionality already sitting
> there.
>
> --Brian
>
> -----Original Message-----
> From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> Sent: Thursday, July 05, 2007 9:21 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> test are missing correct, but a fix for this ear problem is rather
> important because
> ear's won't work with WTP as they are.
>
> Ritchie
>
> Brian E. Fox wrote:
>
>> Same thing with this one, the patch doesn't exist yet along with tests
>> or doc changes. If we have to respin the release because of the test
>> problems, then we can grab a few patches if they are complete,
>>
> otherwise
>
>> I say they wait. We've been discussing releasing for several weeks now
>> and need to pull the trigger at some point. We shouldn't wait another
>>
> 5
>
>> months before releasing again so this doesn't become a problem.
>>
>> -----Original Message-----
>> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
>> Sent: Thursday, July 05, 2007 4:55 AM
>> To: Maven Developers List
>> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>>
>> We just received a comment about MECLIPSE-184 (it was in private
>> before).
>> WDYT ? I'm not a ear user...
>>
>> Arnaud
>>
>>
>> On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>>
>>
>>> It's been about 5 months since an eclipse plugin release and we have
>>> lots of fixes and a handful of enhancements:
>>>
>>> Bug
>>> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>>> javax.servlet:servlet-api:2.3
>>> * [MECLIPSE-109] - .component wb-resource source path incorrect for
>>>
>>>
>> ear
>>
>>
>>> packaging
>>> * [MECLIPSE-151] - Incorrect name for test sources jars
>>> * [MECLIPSE-198] - EJB version is not resloved
>>> * [MECLIPSE-215] - WTP 1.5 Documentation
>>> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
>>> eclipse:eclipse for war and ejb projects.
>>> * [MECLIPSE-225] - Invalid .classpath Entries.
>>> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>>> case-sensitive
>>> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
>>> String method argument causing maven-eclipse.xml copy-resources
>>>
>>>
>> problems
>>
>>
>>> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>>> resolution:=optional directive
>>> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>>> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
>>>
>>>
>> in
>>
>>
>>> wtp facet
>>> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
>>>
>>>
>> Server
>>
>>
>>> to be built
>>> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>>> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
>>>
>>>
>> defined
>>
>>
>>> in pom.xml
>>> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in
>>>
> a
>
>>> Java 5.0 project
>>> * [MECLIPSE-278] - duplicated classpathentries
>>> * [MECLIPSE-279] - PDE projects should be considered java projects in
>>> all cases
>>> * [MECLIPSE-287] - Regression - fails to correctly construct
>>>
> classpath
>
>>> containing dependencies with classifiers
>>> Improvement
>>> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>>> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>>> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>>> version, jsp version, ... possible through pom configuration
>>> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>>> creation while executing eclipse:rad
>>> New Feature
>>> * [MECLIPSE-119] - Allow custom project name for eclipse projects
>>> * [MECLIPSE-189] - addVersionToProjectName property
>>> * [MECLIPSE-251] - Allows prefixing of eclipse project name
>>> * [MECLIPSE-271] - Ability to skip
>>>
>>> The site has been updated:
>>> http://maven.apache.org/plugins/maven-eclipse-plugin
>>>
>>> Plugin is staged here:
>>> http://people.apache.org/~brianf/staging-repository/
>>>
>>> Vote is open for 72hrs.
>>>
>>> +1
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Ritchie,
I understand the issue but on the flip side, without tests to ensure the
functionality works as expected, we can't verify it. I don't personally
use this functionality of the plugin so I can't tell at a glance if it's
right or not. As I see it, once we are this close to a release
(discussion about preparing for it occurred mid-june) then only complete
patches can be considered for inclusion. Otherwise we might have to wait
another week or two until someone has time to analyze and complete the
patch. It's a recurring cycle where we wait and wait and before you know
it, it's 5 months like it is now with good functionality already sitting
there.
--Brian
-----Original Message-----
From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
Sent: Thursday, July 05, 2007 9:21 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4
test are missing correct, but a fix for this ear problem is rather
important because
ear's won't work with WTP as they are.
Ritchie
Brian E. Fox wrote:
> Same thing with this one, the patch doesn't exist yet along with tests
> or doc changes. If we have to respin the release because of the test
> problems, then we can grab a few patches if they are complete,
otherwise
> I say they wait. We've been discussing releasing for several weeks now
> and need to pull the trigger at some point. We shouldn't wait another
5
> months before releasing again so this doesn't become a problem.
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: Thursday, July 05, 2007 4:55 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> We just received a comment about MECLIPSE-184 (it was in private
> before).
> WDYT ? I'm not a ear user...
>
> Arnaud
>
>
> On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
>> It's been about 5 months since an eclipse plugin release and we have
>> lots of fixes and a handful of enhancements:
>>
>> Bug
>> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>> javax.servlet:servlet-api:2.3
>> * [MECLIPSE-109] - .component wb-resource source path incorrect for
>>
> ear
>
>> packaging
>> * [MECLIPSE-151] - Incorrect name for test sources jars
>> * [MECLIPSE-198] - EJB version is not resloved
>> * [MECLIPSE-215] - WTP 1.5 Documentation
>> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
>> eclipse:eclipse for war and ejb projects.
>> * [MECLIPSE-225] - Invalid .classpath Entries.
>> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>> case-sensitive
>> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
>> String method argument causing maven-eclipse.xml copy-resources
>>
> problems
>
>> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>> resolution:=optional directive
>> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
>>
> in
>
>> wtp facet
>> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
>>
> Server
>
>> to be built
>> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
>>
> defined
>
>> in pom.xml
>> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in
a
>> Java 5.0 project
>> * [MECLIPSE-278] - duplicated classpathentries
>> * [MECLIPSE-279] - PDE projects should be considered java projects in
>> all cases
>> * [MECLIPSE-287] - Regression - fails to correctly construct
classpath
>> containing dependencies with classifiers
>> Improvement
>> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>> version, jsp version, ... possible through pom configuration
>> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>> creation while executing eclipse:rad
>> New Feature
>> * [MECLIPSE-119] - Allow custom project name for eclipse projects
>> * [MECLIPSE-189] - addVersionToProjectName property
>> * [MECLIPSE-251] - Allows prefixing of eclipse project name
>> * [MECLIPSE-271] - Ability to skip
>>
>> The site has been updated:
>> http://maven.apache.org/plugins/maven-eclipse-plugin
>>
>> Plugin is staged here:
>> http://people.apache.org/~brianf/staging-repository/
>>
>> Vote is open for 72hrs.
>>
>> +1
>>
>>
>> ---------------------------------------------------------------------
>> 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] maven-eclipse-plugin 2.4
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
test are missing correct, but a fix for this ear problem is rather
important because
ear's won't work with WTP as they are.
Ritchie
Brian E. Fox wrote:
> Same thing with this one, the patch doesn't exist yet along with tests
> or doc changes. If we have to respin the release because of the test
> problems, then we can grab a few patches if they are complete, otherwise
> I say they wait. We've been discussing releasing for several weeks now
> and need to pull the trigger at some point. We shouldn't wait another 5
> months before releasing again so this doesn't become a problem.
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: Thursday, July 05, 2007 4:55 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> We just received a comment about MECLIPSE-184 (it was in private
> before).
> WDYT ? I'm not a ear user...
>
> Arnaud
>
>
> On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
>> It's been about 5 months since an eclipse plugin release and we have
>> lots of fixes and a handful of enhancements:
>>
>> Bug
>> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>> javax.servlet:servlet-api:2.3
>> * [MECLIPSE-109] - .component wb-resource source path incorrect for
>>
> ear
>
>> packaging
>> * [MECLIPSE-151] - Incorrect name for test sources jars
>> * [MECLIPSE-198] - EJB version is not resloved
>> * [MECLIPSE-215] - WTP 1.5 Documentation
>> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
>> eclipse:eclipse for war and ejb projects.
>> * [MECLIPSE-225] - Invalid .classpath Entries.
>> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>> case-sensitive
>> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
>> String method argument causing maven-eclipse.xml copy-resources
>>
> problems
>
>> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>> resolution:=optional directive
>> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
>>
> in
>
>> wtp facet
>> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
>>
> Server
>
>> to be built
>> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
>>
> defined
>
>> in pom.xml
>> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
>> Java 5.0 project
>> * [MECLIPSE-278] - duplicated classpathentries
>> * [MECLIPSE-279] - PDE projects should be considered java projects in
>> all cases
>> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
>> containing dependencies with classifiers
>> Improvement
>> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>> version, jsp version, ... possible through pom configuration
>> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>> creation while executing eclipse:rad
>> New Feature
>> * [MECLIPSE-119] - Allow custom project name for eclipse projects
>> * [MECLIPSE-189] - addVersionToProjectName property
>> * [MECLIPSE-251] - Allows prefixing of eclipse project name
>> * [MECLIPSE-271] - Ability to skip
>>
>> The site has been updated:
>> http://maven.apache.org/plugins/maven-eclipse-plugin
>>
>> Plugin is staged here:
>> http://people.apache.org/~brianf/staging-repository/
>>
>> Vote is open for 72hrs.
>>
>> +1
>>
>>
>> ---------------------------------------------------------------------
>> 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] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Same thing with this one, the patch doesn't exist yet along with tests
or doc changes. If we have to respin the release because of the test
problems, then we can grab a few patches if they are complete, otherwise
I say they wait. We've been discussing releasing for several weeks now
and need to pull the trigger at some point. We shouldn't wait another 5
months before releasing again so this doesn't become a problem.
-----Original Message-----
From: Arnaud HERITIER [mailto:aheritier@gmail.com]
Sent: Thursday, July 05, 2007 4:55 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4
We just received a comment about MECLIPSE-184 (it was in private
before).
WDYT ? I'm not a ear user...
Arnaud
On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements:
>
> Bug
> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> javax.servlet:servlet-api:2.3
> * [MECLIPSE-109] - .component wb-resource source path incorrect for
ear
> packaging
> * [MECLIPSE-151] - Incorrect name for test sources jars
> * [MECLIPSE-198] - EJB version is not resloved
> * [MECLIPSE-215] - WTP 1.5 Documentation
> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> eclipse:eclipse for war and ejb projects.
> * [MECLIPSE-225] - Invalid .classpath Entries.
> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> case-sensitive
> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> String method argument causing maven-eclipse.xml copy-resources
problems
> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> resolution:=optional directive
> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
in
> wtp facet
> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
Server
> to be built
> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
defined
> in pom.xml
> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> Java 5.0 project
> * [MECLIPSE-278] - duplicated classpathentries
> * [MECLIPSE-279] - PDE projects should be considered java projects in
> all cases
> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> containing dependencies with classifiers
> Improvement
> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> version, jsp version, ... possible through pom configuration
> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> creation while executing eclipse:rad
> New Feature
> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> * [MECLIPSE-189] - addVersionToProjectName property
> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> * [MECLIPSE-271] - Ability to skip
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/staging-repository/
>
> Vote is open for 72hrs.
>
> +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@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Arnaud HERITIER <ah...@gmail.com>.
Seems to be fine.
I wait to see with Brian what we do to see if I can apply it.
Thanks for your help
Arnaud
On 05/07/07, Richard van Nieuwenhoven <ni...@cfc.at> wrote:
> Hello,
>
> my patch http://jira.codehaus.org/browse/MECLIPSE-213 contains a fix for
> this problem.
> i have also a better version that takes it from the ear-plugin
> configuration because there
> there is a property *defaultLibBundleDir
> <http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html#defaultLibBundleDir>
> *that should be used to specify the directory, i can
> post it if you need it.
>
> Ritchie
>
> Arnaud HERITIER wrote:
> > Brian, what do we do ?
> > We fix it for 2.4 or not ?
> >
> > On 05/07/07, Cabasson Denis <de...@insee.fr> wrote:
> >> Looks relevant to me. In a EAR you indeed expect dependencies to be
> >> in the root directory, not under WEB-INF lib.
> >>
> >> Suggested solution looks sensible.
> >>
> >> Denis.
> >>
> >> > -----Message d'origine-----
> >> > De : Arnaud HERITIER [mailto:aheritier@gmail.com]
> >> > Envoyé : Thursday, July 05, 2007 10:55 AM
> >> > À : Maven Developers List
> >> > Objet : Re: [VOTE] maven-eclipse-plugin 2.4
> >> >
> >> > We just received a comment about MECLIPSE-184 (it was in
> >> > private before).
> >> > WDYT ? I'm not a ear user...
> >> >
> >> > Arnaud
> >> >
> >> >
> >> > On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >> > > It's been about 5 months since an eclipse plugin release
> >> > and we have
> >> > > lots of fixes and a handful of enhancements:
> >> > >
> >> > > Bug
> >> > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> >> > > javax.servlet:servlet-api:2.3
> >> > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> >> > > ear packaging
> >> > > * [MECLIPSE-151] - Incorrect name for test sources jars
> >> > > * [MECLIPSE-198] - EJB version is not resloved
> >> > > * [MECLIPSE-215] - WTP 1.5 Documentation
> >> > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> >> > doing mvn
> >> > > eclipse:eclipse for war and ejb projects.
> >> > > * [MECLIPSE-225] - Invalid .classpath Entries.
> >> > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> >> > > case-sensitive
> >> > > * [MECLIPSE-234] - [PATCH]
> >> > EclipsePlugin.extractResourceDirs() reuses
> >> > > String method argument causing maven-eclipse.xml copy-resources
> >> > > problems
> >> > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> >> > > resolution:=optional directive
> >> > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> >> > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> >> > aren't used
> >> > > in wtp facet
> >> > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> >> > > Server to be built
> >> > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> >> > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> >> > > defined in pom.xml
> >> > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> >> > of 5.0 in a
> >> > > Java 5.0 project
> >> > > * [MECLIPSE-278] - duplicated classpathentries
> >> > > * [MECLIPSE-279] - PDE projects should be considered java
> >> > projects in
> >> > > all cases
> >> > > * [MECLIPSE-287] - Regression - fails to correctly
> >> > construct classpath
> >> > > containing dependencies with classifiers Improvement
> >> > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> >> > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> >> > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> >> > > version, jsp version, ... possible through pom configuration
> >> > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> >> > > creation while executing eclipse:rad New Feature
> >> > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> >> > > * [MECLIPSE-189] - addVersionToProjectName property
> >> > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> >> > > * [MECLIPSE-271] - Ability to skip
> >> > >
> >> > > The site has been updated:
> >> > > http://maven.apache.org/plugins/maven-eclipse-plugin
> >> > >
> >> > > Plugin is staged here:
> >> > > http://people.apache.org/~brianf/staging-repository/
> >> > >
> >> > > Vote is open for 72hrs.
> >> > >
> >> > > +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@octo.com
> >> > www.octo.com | blog.octo.com
> >> > ..........................................................
> >> > ASF - aheritier@apache.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@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Arnaud HERITIER <ah...@gmail.com>.
It's why I didn't apply it the last time I reviewed WTP issues,
because it cost to me a too long time to add those missing elements...
Arnaud
On 05/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> I don't see any tests or docs included in the patch. If we want to apply something quickly, it needs to have all the pieces, otherwise it would have to wait until someone has time to essentially complete the fix.
>
> -----Original Message-----
> From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
> Sent: Thursday, July 05, 2007 7:06 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> Hello,
>
> my patch http://jira.codehaus.org/browse/MECLIPSE-213 contains a fix for
> this problem.
> i have also a better version that takes it from the ear-plugin
> configuration because there
> there is a property *defaultLibBundleDir
> <http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html#defaultLibBundleDir>
> *that should be used to specify the directory, i can
> post it if you need it.
>
> Ritchie
>
> Arnaud HERITIER wrote:
> > Brian, what do we do ?
> > We fix it for 2.4 or not ?
> >
> > On 05/07/07, Cabasson Denis <de...@insee.fr> wrote:
> >> Looks relevant to me. In a EAR you indeed expect dependencies to be
> >> in the root directory, not under WEB-INF lib.
> >>
> >> Suggested solution looks sensible.
> >>
> >> Denis.
> >>
> >> > -----Message d'origine-----
> >> > De : Arnaud HERITIER [mailto:aheritier@gmail.com]
> >> > Envoyé : Thursday, July 05, 2007 10:55 AM
> >> > À : Maven Developers List
> >> > Objet : Re: [VOTE] maven-eclipse-plugin 2.4
> >> >
> >> > We just received a comment about MECLIPSE-184 (it was in
> >> > private before).
> >> > WDYT ? I'm not a ear user...
> >> >
> >> > Arnaud
> >> >
> >> >
> >> > On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >> > > It's been about 5 months since an eclipse plugin release
> >> > and we have
> >> > > lots of fixes and a handful of enhancements:
> >> > >
> >> > > Bug
> >> > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> >> > > javax.servlet:servlet-api:2.3
> >> > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> >> > > ear packaging
> >> > > * [MECLIPSE-151] - Incorrect name for test sources jars
> >> > > * [MECLIPSE-198] - EJB version is not resloved
> >> > > * [MECLIPSE-215] - WTP 1.5 Documentation
> >> > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> >> > doing mvn
> >> > > eclipse:eclipse for war and ejb projects.
> >> > > * [MECLIPSE-225] - Invalid .classpath Entries.
> >> > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> >> > > case-sensitive
> >> > > * [MECLIPSE-234] - [PATCH]
> >> > EclipsePlugin.extractResourceDirs() reuses
> >> > > String method argument causing maven-eclipse.xml copy-resources
> >> > > problems
> >> > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> >> > > resolution:=optional directive
> >> > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> >> > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> >> > aren't used
> >> > > in wtp facet
> >> > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> >> > > Server to be built
> >> > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> >> > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> >> > > defined in pom.xml
> >> > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> >> > of 5.0 in a
> >> > > Java 5.0 project
> >> > > * [MECLIPSE-278] - duplicated classpathentries
> >> > > * [MECLIPSE-279] - PDE projects should be considered java
> >> > projects in
> >> > > all cases
> >> > > * [MECLIPSE-287] - Regression - fails to correctly
> >> > construct classpath
> >> > > containing dependencies with classifiers Improvement
> >> > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> >> > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> >> > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> >> > > version, jsp version, ... possible through pom configuration
> >> > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> >> > > creation while executing eclipse:rad New Feature
> >> > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> >> > > * [MECLIPSE-189] - addVersionToProjectName property
> >> > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> >> > > * [MECLIPSE-271] - Ability to skip
> >> > >
> >> > > The site has been updated:
> >> > > http://maven.apache.org/plugins/maven-eclipse-plugin
> >> > >
> >> > > Plugin is staged here:
> >> > > http://people.apache.org/~brianf/staging-repository/
> >> > >
> >> > > Vote is open for 72hrs.
> >> > >
> >> > > +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@octo.com
> >> > www.octo.com | blog.octo.com
> >> > ..........................................................
> >> > ASF - aheritier@apache.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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I don't see any tests or docs included in the patch. If we want to apply something quickly, it needs to have all the pieces, otherwise it would have to wait until someone has time to essentially complete the fix.
-----Original Message-----
From: Richard van Nieuwenhoven [mailto:nir@cfc.at]
Sent: Thursday, July 05, 2007 7:06 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4
Hello,
my patch http://jira.codehaus.org/browse/MECLIPSE-213 contains a fix for
this problem.
i have also a better version that takes it from the ear-plugin
configuration because there
there is a property *defaultLibBundleDir
<http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html#defaultLibBundleDir>
*that should be used to specify the directory, i can
post it if you need it.
Ritchie
Arnaud HERITIER wrote:
> Brian, what do we do ?
> We fix it for 2.4 or not ?
>
> On 05/07/07, Cabasson Denis <de...@insee.fr> wrote:
>> Looks relevant to me. In a EAR you indeed expect dependencies to be
>> in the root directory, not under WEB-INF lib.
>>
>> Suggested solution looks sensible.
>>
>> Denis.
>>
>> > -----Message d'origine-----
>> > De : Arnaud HERITIER [mailto:aheritier@gmail.com]
>> > Envoyé : Thursday, July 05, 2007 10:55 AM
>> > À : Maven Developers List
>> > Objet : Re: [VOTE] maven-eclipse-plugin 2.4
>> >
>> > We just received a comment about MECLIPSE-184 (it was in
>> > private before).
>> > WDYT ? I'm not a ear user...
>> >
>> > Arnaud
>> >
>> >
>> > On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>> > > It's been about 5 months since an eclipse plugin release
>> > and we have
>> > > lots of fixes and a handful of enhancements:
>> > >
>> > > Bug
>> > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>> > > javax.servlet:servlet-api:2.3
>> > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
>> > > ear packaging
>> > > * [MECLIPSE-151] - Incorrect name for test sources jars
>> > > * [MECLIPSE-198] - EJB version is not resloved
>> > > * [MECLIPSE-215] - WTP 1.5 Documentation
>> > > * [MECLIPSE-220] - Incorrect eclipse facet information when
>> > doing mvn
>> > > eclipse:eclipse for war and ejb projects.
>> > > * [MECLIPSE-225] - Invalid .classpath Entries.
>> > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>> > > case-sensitive
>> > > * [MECLIPSE-234] - [PATCH]
>> > EclipsePlugin.extractResourceDirs() reuses
>> > > String method argument causing maven-eclipse.xml copy-resources
>> > > problems
>> > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>> > > resolution:=optional directive
>> > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>> > > * [MECLIPSE-241] - Compiler settings in pluginManagement
>> > aren't used
>> > > in wtp facet
>> > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
>> > > Server to be built
>> > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>> > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
>> > > defined in pom.xml
>> > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
>> > of 5.0 in a
>> > > Java 5.0 project
>> > > * [MECLIPSE-278] - duplicated classpathentries
>> > > * [MECLIPSE-279] - PDE projects should be considered java
>> > projects in
>> > > all cases
>> > > * [MECLIPSE-287] - Regression - fails to correctly
>> > construct classpath
>> > > containing dependencies with classifiers Improvement
>> > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>> > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>> > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>> > > version, jsp version, ... possible through pom configuration
>> > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>> > > creation while executing eclipse:rad New Feature
>> > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
>> > > * [MECLIPSE-189] - addVersionToProjectName property
>> > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
>> > > * [MECLIPSE-271] - Ability to skip
>> > >
>> > > The site has been updated:
>> > > http://maven.apache.org/plugins/maven-eclipse-plugin
>> > >
>> > > Plugin is staged here:
>> > > http://people.apache.org/~brianf/staging-repository/
>> > >
>> > > Vote is open for 72hrs.
>> > >
>> > > +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@octo.com
>> > www.octo.com | blog.octo.com
>> > ..........................................................
>> > ASF - aheritier@apache.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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Richard van Nieuwenhoven <ni...@cfc.at>.
Hello,
my patch http://jira.codehaus.org/browse/MECLIPSE-213 contains a fix for
this problem.
i have also a better version that takes it from the ear-plugin
configuration because there
there is a property *defaultLibBundleDir
<http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html#defaultLibBundleDir>
*that should be used to specify the directory, i can
post it if you need it.
Ritchie
Arnaud HERITIER wrote:
> Brian, what do we do ?
> We fix it for 2.4 or not ?
>
> On 05/07/07, Cabasson Denis <de...@insee.fr> wrote:
>> Looks relevant to me. In a EAR you indeed expect dependencies to be
>> in the root directory, not under WEB-INF lib.
>>
>> Suggested solution looks sensible.
>>
>> Denis.
>>
>> > -----Message d'origine-----
>> > De : Arnaud HERITIER [mailto:aheritier@gmail.com]
>> > Envoyé : Thursday, July 05, 2007 10:55 AM
>> > À : Maven Developers List
>> > Objet : Re: [VOTE] maven-eclipse-plugin 2.4
>> >
>> > We just received a comment about MECLIPSE-184 (it was in
>> > private before).
>> > WDYT ? I'm not a ear user...
>> >
>> > Arnaud
>> >
>> >
>> > On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>> > > It's been about 5 months since an eclipse plugin release
>> > and we have
>> > > lots of fixes and a handful of enhancements:
>> > >
>> > > Bug
>> > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>> > > javax.servlet:servlet-api:2.3
>> > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
>> > > ear packaging
>> > > * [MECLIPSE-151] - Incorrect name for test sources jars
>> > > * [MECLIPSE-198] - EJB version is not resloved
>> > > * [MECLIPSE-215] - WTP 1.5 Documentation
>> > > * [MECLIPSE-220] - Incorrect eclipse facet information when
>> > doing mvn
>> > > eclipse:eclipse for war and ejb projects.
>> > > * [MECLIPSE-225] - Invalid .classpath Entries.
>> > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>> > > case-sensitive
>> > > * [MECLIPSE-234] - [PATCH]
>> > EclipsePlugin.extractResourceDirs() reuses
>> > > String method argument causing maven-eclipse.xml copy-resources
>> > > problems
>> > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>> > > resolution:=optional directive
>> > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>> > > * [MECLIPSE-241] - Compiler settings in pluginManagement
>> > aren't used
>> > > in wtp facet
>> > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
>> > > Server to be built
>> > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>> > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
>> > > defined in pom.xml
>> > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
>> > of 5.0 in a
>> > > Java 5.0 project
>> > > * [MECLIPSE-278] - duplicated classpathentries
>> > > * [MECLIPSE-279] - PDE projects should be considered java
>> > projects in
>> > > all cases
>> > > * [MECLIPSE-287] - Regression - fails to correctly
>> > construct classpath
>> > > containing dependencies with classifiers Improvement
>> > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>> > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>> > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>> > > version, jsp version, ... possible through pom configuration
>> > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>> > > creation while executing eclipse:rad New Feature
>> > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
>> > > * [MECLIPSE-189] - addVersionToProjectName property
>> > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
>> > > * [MECLIPSE-271] - Ability to skip
>> > >
>> > > The site has been updated:
>> > > http://maven.apache.org/plugins/maven-eclipse-plugin
>> > >
>> > > Plugin is staged here:
>> > > http://people.apache.org/~brianf/staging-repository/
>> > >
>> > > Vote is open for 72hrs.
>> > >
>> > > +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@octo.com
>> > www.octo.com | blog.octo.com
>> > ..........................................................
>> > ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Arnaud HERITIER <ah...@gmail.com>.
Brian, what do we do ?
We fix it for 2.4 or not ?
On 05/07/07, Cabasson Denis <de...@insee.fr> wrote:
> Looks relevant to me. In a EAR you indeed expect dependencies to be in the root directory, not under WEB-INF lib.
>
> Suggested solution looks sensible.
>
> Denis.
>
> > -----Message d'origine-----
> > De : Arnaud HERITIER [mailto:aheritier@gmail.com]
> > Envoyé : Thursday, July 05, 2007 10:55 AM
> > À : Maven Developers List
> > Objet : Re: [VOTE] maven-eclipse-plugin 2.4
> >
> > We just received a comment about MECLIPSE-184 (it was in
> > private before).
> > WDYT ? I'm not a ear user...
> >
> > Arnaud
> >
> >
> > On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > It's been about 5 months since an eclipse plugin release
> > and we have
> > > lots of fixes and a handful of enhancements:
> > >
> > > Bug
> > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > javax.servlet:servlet-api:2.3
> > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> > > ear packaging
> > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > * [MECLIPSE-198] - EJB version is not resloved
> > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> > doing mvn
> > > eclipse:eclipse for war and ejb projects.
> > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > case-sensitive
> > > * [MECLIPSE-234] - [PATCH]
> > EclipsePlugin.extractResourceDirs() reuses
> > > String method argument causing maven-eclipse.xml copy-resources
> > > problems
> > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > resolution:=optional directive
> > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > aren't used
> > > in wtp facet
> > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> > > Server to be built
> > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> > > defined in pom.xml
> > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> > of 5.0 in a
> > > Java 5.0 project
> > > * [MECLIPSE-278] - duplicated classpathentries
> > > * [MECLIPSE-279] - PDE projects should be considered java
> > projects in
> > > all cases
> > > * [MECLIPSE-287] - Regression - fails to correctly
> > construct classpath
> > > containing dependencies with classifiers Improvement
> > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> > > version, jsp version, ... possible through pom configuration
> > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> > > creation while executing eclipse:rad New Feature
> > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> > > * [MECLIPSE-189] - addVersionToProjectName property
> > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > * [MECLIPSE-271] - Ability to skip
> > >
> > > The site has been updated:
> > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > >
> > > Plugin is staged here:
> > > http://people.apache.org/~brianf/staging-repository/
> > >
> > > Vote is open for 72hrs.
> > >
> > > +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@octo.com
> > www.octo.com | blog.octo.com
> > ..........................................................
> > ASF - aheritier@apache.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@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Cabasson Denis <de...@insee.fr>.
Looks relevant to me. In a EAR you indeed expect dependencies to be in the root directory, not under WEB-INF lib.
Suggested solution looks sensible.
Denis.
> -----Message d'origine-----
> De : Arnaud HERITIER [mailto:aheritier@gmail.com]
> Envoyé : Thursday, July 05, 2007 10:55 AM
> À : Maven Developers List
> Objet : Re: [VOTE] maven-eclipse-plugin 2.4
>
> We just received a comment about MECLIPSE-184 (it was in
> private before).
> WDYT ? I'm not a ear user...
>
> Arnaud
>
>
> On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > It's been about 5 months since an eclipse plugin release
> and we have
> > lots of fixes and a handful of enhancements:
> >
> > Bug
> > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > javax.servlet:servlet-api:2.3
> > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> > ear packaging
> > * [MECLIPSE-151] - Incorrect name for test sources jars
> > * [MECLIPSE-198] - EJB version is not resloved
> > * [MECLIPSE-215] - WTP 1.5 Documentation
> > * [MECLIPSE-220] - Incorrect eclipse facet information when
> doing mvn
> > eclipse:eclipse for war and ejb projects.
> > * [MECLIPSE-225] - Invalid .classpath Entries.
> > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > case-sensitive
> > * [MECLIPSE-234] - [PATCH]
> EclipsePlugin.extractResourceDirs() reuses
> > String method argument causing maven-eclipse.xml copy-resources
> > problems
> > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > resolution:=optional directive
> > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > * [MECLIPSE-241] - Compiler settings in pluginManagement
> aren't used
> > in wtp facet
> > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> > Server to be built
> > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> > defined in pom.xml
> > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> of 5.0 in a
> > Java 5.0 project
> > * [MECLIPSE-278] - duplicated classpathentries
> > * [MECLIPSE-279] - PDE projects should be considered java
> projects in
> > all cases
> > * [MECLIPSE-287] - Regression - fails to correctly
> construct classpath
> > containing dependencies with classifiers Improvement
> > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> > version, jsp version, ... possible through pom configuration
> > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> > creation while executing eclipse:rad New Feature
> > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> > * [MECLIPSE-189] - addVersionToProjectName property
> > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > * [MECLIPSE-271] - Ability to skip
> >
> > The site has been updated:
> > http://maven.apache.org/plugins/maven-eclipse-plugin
> >
> > Plugin is staged here:
> > http://people.apache.org/~brianf/staging-repository/
> >
> > Vote is open for 72hrs.
> >
> > +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@octo.com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier@apache.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] maven-eclipse-plugin 2.4
Posted by Arnaud HERITIER <ah...@gmail.com>.
We just received a comment about MECLIPSE-184 (it was in private before).
WDYT ? I'm not a ear user...
Arnaud
On 04/07/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements:
>
> Bug
> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> javax.servlet:servlet-api:2.3
> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear
> packaging
> * [MECLIPSE-151] - Incorrect name for test sources jars
> * [MECLIPSE-198] - EJB version is not resloved
> * [MECLIPSE-215] - WTP 1.5 Documentation
> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> eclipse:eclipse for war and ejb projects.
> * [MECLIPSE-225] - Invalid .classpath Entries.
> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> case-sensitive
> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> String method argument causing maven-eclipse.xml copy-resources problems
> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> resolution:=optional directive
> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
> wtp facet
> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
> to be built
> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
> in pom.xml
> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> Java 5.0 project
> * [MECLIPSE-278] - duplicated classpathentries
> * [MECLIPSE-279] - PDE projects should be considered java projects in
> all cases
> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> containing dependencies with classifiers
> Improvement
> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> version, jsp version, ... possible through pom configuration
> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> creation while executing eclipse:rad
> New Feature
> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> * [MECLIPSE-189] - addVersionToProjectName property
> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> * [MECLIPSE-271] - Ability to skip
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/staging-repository/
>
> Vote is open for 72hrs.
>
> +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@octo.com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier@apache.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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Somehow maven has decided it wants the test version, which obviously
doesn't exist. We need to figure out where it got that info from.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 11:50 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
no proxy in the middle, just did it again with a clean local repo
[INFO] [eclipse:eclipse]
[INFO] Not running eclipse plugin goal for pom project
[INFO]
------------------------------------------------------------------------
-
---
[INFO] Building Maven SCM API
[INFO] task-segment: [eclipse:eclipse]
[INFO]
------------------------------------------------------------------------
-
---
[INFO] Preparing eclipse:eclipse
Downloading:
http://people.apache.org/~brianf/staging-repository/org/apache/mave
n/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclips
e-plugin/test/maven-eclipse-plugin-test.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclips
e-plugin/test/maven-eclipse-plugin-test.pom
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-eclipse-plugin
Version: test
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-eclipse-plugin:pom:test
from the specified remote repositories:
Remote resources plugin staging repository (
http://people.apache.org/~brianf/s
taging-repository),
central (http://repo1.maven.org/maven2),
apache.snapshots
(http://people.apache.org/repo/m2-snapshot-repository)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 14 seconds
[INFO] Finished at: Fri Jul 06 08:48:26 PDT 2007
[INFO] Final Memory: 4M/7M
[INFO]
------------------------------------------------------------------------
C:\dev\maven\src\scm>
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> I'm still not able to get any issues, even when I get 2.4 downloaded.
Do
> you have a proxy that might be in the way?
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 10:41 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> mvn eclipse:eclipse -P brianf-repo
>
> I use brianf-repo profile to pickup 2.4
>
> -D
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > See this is where I'm lost. If maven can't even find the eclipse
> plugin
> > to start with, how could this be a problem with 2.4 specifically?
The
> > comments in MECLIPSE-248 from Carlos said that if he clears his repo
> and
> > lets it download, it fails. That's what I did and it worked.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 10:01 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > eclipse-2.4
> >
> > -Dan
> >
> >
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I just tried with maven-native after clearing my repo. It
correctly
> > > downloads 2.3 and runs a-ok.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 9:54 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > One more fact on this, I am currently used an internal released
> > version
> > > of
> > > eclipse plugin at
> > > r541399, and it works for us. Could there be some changes in
> between
> > > that
> > > may have
> > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > >
> > > -D
> > >
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > I don't think this is directly a plugin problem. I think there
is
> > some
> > > > stray metadata floating in a repo somewhere, possibly left from
a
> > bad
> > > > build of the unit tests, which use "test" as the version.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > cool, at least someone sees what i see. So this 2.4 release is
a
> > > nogo.
> > > > -1
> > > > from me.
> > > >
> > > > we should reopen MECLIPSE-248 as well right?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > >
> > > > > I wrote my problems with it in MECLIPSE-248
> > > > >
> > > > > * the only way to get it work so far is delete the
> > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > local
> > > > > repo and install the plugin locally
> > > > > * if you install without removing the folder doesn't work
> > > > > * if you remove the folder and let it get downloaded doesn't
> work
> > > > >
> > > > >
> > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > The problem reproducable with maven-scm project even with
> clean
> > > > local
> > > > > repo.
> > > > > >
> > > > > > I happens on all of my known projects ( ie maven-native at
> mojo
> > > > > ). Note
> > > > > > all projects
> > > > > > involve reactor mode. Single project seems to be working
> > > > > >
> > > > > > Can some one confirm?
> > > > > >
> > > > > > -D
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > Dan, I saw this on IRC the other day. It was related to
some
> > > > > repository
> > > > > > > entries in the project itself, presumably those repos
> > contained
> > > > bad
> > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > MECLIPSE-248,
> > > > > I
> > > > > > > pasted the IRC log url in there.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> SUMMARY)
> > > > > > >
> > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > > > [ERROR] BUILD ERROR
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > > > [INFO] Failed to resolve artifact.
> > > > > > >
> > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > Version: test
> > > > > > >
> > > > > > > Reason: Unable to download the artifact from any
repository
> > > > > > >
> > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > >
> > > > > > >
> > > > > > > I am using brainf's staged plugin and both built 2.4 tag
and
> > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > All give the same error
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > any suggestions on how to debug this error?
> > > > > > > -Dan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > >
> > > > > > > > There's been a lot of discussion in this thread about
the
> > > > release.
> > > > > Let
> > > > > > > > me summarize for those trying to keep up:
> > > > > > > >
> > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > Non-Binding: +1 Graham
> > > > > > > >
> > > > > > > > There are some transient issues with the test subsystem
> used
> > > by
> > > > > > > eclipse
> > > > > > > > that cause failures on Solaris. The issues are with the
> test
> > > > tools
> > > > > > > > themselves, when the tests execute properly, everything
> > passes
> > > > and
> > > > > > > thus
> > > > > > > > the plugin is doing the correct thing (for the tests
that
> > > exist
> > > > > anyway
> > > > > > > > ;-) )
> > > > > > > >
> > > > > > > > At this point, the vote has enough PMC support to
release
> > and
> > > > will
> > > > > > > > continue for the remaining ~53hrs. Unless a veto
arrives,
> > the
> > > > > release
> > > > > > > > should occur over the weekend.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > To: Maven Developers List
> > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > >
> > > > > > > > It's been about 5 months since an eclipse plugin release
> and
> > > we
> > > > have
> > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > >
> > > > > > > > Bug
> > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > incorrect
> > > > for
> > > > > > > ear
> > > > > > > > packaging
> > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
> when
> > > > doing
> > > > > mvn
> > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly
treated
> > as
> > > > > > > > case-sensitive
> > > > > > > > * [MECLIPSE-234] - [PATCH]
> > EclipsePlugin.extractResourceDirs()
> > > > > reuses
> > > > > > > > String method argument causing maven-eclipse.xml
> > > copy-resources
> > > > > > > problems
> > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should
preserve
> > the
> > > > > > > > resolution:=optional directive
> > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals()
method
> > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > aren't
> > > > used
> > > > > > > in
> > > > > > > > wtp facet
> > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > Directory
> > > > > > > Server
> > > > > > > > to be built
> > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > "test"
> > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > version
> > > > > > > defined
> > > > > > > > in pom.xml
> > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4
instead
> > of
> > > > 5.0 in
> > > > > a
> > > > > > > > Java 5.0 project
> > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > * [MECLIPSE-279] - PDE projects should be considered
java
> > > > projects
> > > > > in
> > > > > > > > all cases
> > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> construct
> > > > > classpath
> > > > > > > > containing dependencies with classifiers
> > > > > > > > Improvement
> > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
> JSF
> > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> make-artifacts
> > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
> of
> > > > servlet
> > > > > > > > version, jsp version, ... possible through pom
> configuration
> > > > > > > > * [MECLIPSE-286] - Ability to skip
> generated-resources/rad6
> > > > folder
> > > > > > > > creation while executing eclipse:rad
> > > > > > > > New Feature
> > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > projects
> > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
> name
> > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > >
> > > > > > > > The site has been updated:
> > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > >
> > > > > > > > Plugin is staged here:
> > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > >
> > > > > > > > Vote is open for 72hrs.
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > I could give you my word as a Spaniard.
> > > > > No good. I've known too many Spaniards.
> > > > > -- The Princess Bride
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > 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
> >
> >
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
no proxy in the middle, just did it again with a clean local repo
[INFO] [eclipse:eclipse]
[INFO] Not running eclipse plugin goal for pom project
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building Maven SCM API
[INFO] task-segment: [eclipse:eclipse]
[INFO]
-------------------------------------------------------------------------
---
[INFO] Preparing eclipse:eclipse
Downloading:
http://people.apache.org/~brianf/staging-repository/org/apache/mave
n/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclips
e-plugin/test/maven-eclipse-plugin-test.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclips
e-plugin/test/maven-eclipse-plugin-test.pom
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-eclipse-plugin
Version: test
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-eclipse-plugin:pom:test
from the specified remote repositories:
Remote resources plugin staging repository (
http://people.apache.org/~brianf/s
taging-repository),
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 14 seconds
[INFO] Finished at: Fri Jul 06 08:48:26 PDT 2007
[INFO] Final Memory: 4M/7M
[INFO]
------------------------------------------------------------------------
C:\dev\maven\src\scm>
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> I'm still not able to get any issues, even when I get 2.4 downloaded. Do
> you have a proxy that might be in the way?
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 10:41 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> mvn eclipse:eclipse -P brianf-repo
>
> I use brianf-repo profile to pickup 2.4
>
> -D
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > See this is where I'm lost. If maven can't even find the eclipse
> plugin
> > to start with, how could this be a problem with 2.4 specifically? The
> > comments in MECLIPSE-248 from Carlos said that if he clears his repo
> and
> > lets it download, it fails. That's what I did and it worked.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 10:01 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > eclipse-2.4
> >
> > -Dan
> >
> >
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I just tried with maven-native after clearing my repo. It correctly
> > > downloads 2.3 and runs a-ok.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 9:54 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > One more fact on this, I am currently used an internal released
> > version
> > > of
> > > eclipse plugin at
> > > r541399, and it works for us. Could there be some changes in
> between
> > > that
> > > may have
> > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > >
> > > -D
> > >
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > I don't think this is directly a plugin problem. I think there is
> > some
> > > > stray metadata floating in a repo somewhere, possibly left from a
> > bad
> > > > build of the unit tests, which use "test" as the version.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > cool, at least someone sees what i see. So this 2.4 release is a
> > > nogo.
> > > > -1
> > > > from me.
> > > >
> > > > we should reopen MECLIPSE-248 as well right?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > >
> > > > > I wrote my problems with it in MECLIPSE-248
> > > > >
> > > > > * the only way to get it work so far is delete the
> > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > local
> > > > > repo and install the plugin locally
> > > > > * if you install without removing the folder doesn't work
> > > > > * if you remove the folder and let it get downloaded doesn't
> work
> > > > >
> > > > >
> > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > The problem reproducable with maven-scm project even with
> clean
> > > > local
> > > > > repo.
> > > > > >
> > > > > > I happens on all of my known projects ( ie maven-native at
> mojo
> > > > > ). Note
> > > > > > all projects
> > > > > > involve reactor mode. Single project seems to be working
> > > > > >
> > > > > > Can some one confirm?
> > > > > >
> > > > > > -D
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > > repository
> > > > > > > entries in the project itself, presumably those repos
> > contained
> > > > bad
> > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > MECLIPSE-248,
> > > > > I
> > > > > > > pasted the IRC log url in there.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> SUMMARY)
> > > > > > >
> > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > > [ERROR] BUILD ERROR
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > > [INFO] Failed to resolve artifact.
> > > > > > >
> > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > Version: test
> > > > > > >
> > > > > > > Reason: Unable to download the artifact from any repository
> > > > > > >
> > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > >
> > > > > > >
> > > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > All give the same error
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > any suggestions on how to debug this error?
> > > > > > > -Dan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > >
> > > > > > > > There's been a lot of discussion in this thread about the
> > > > release.
> > > > > Let
> > > > > > > > me summarize for those trying to keep up:
> > > > > > > >
> > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > Non-Binding: +1 Graham
> > > > > > > >
> > > > > > > > There are some transient issues with the test subsystem
> used
> > > by
> > > > > > > eclipse
> > > > > > > > that cause failures on Solaris. The issues are with the
> test
> > > > tools
> > > > > > > > themselves, when the tests execute properly, everything
> > passes
> > > > and
> > > > > > > thus
> > > > > > > > the plugin is doing the correct thing (for the tests that
> > > exist
> > > > > anyway
> > > > > > > > ;-) )
> > > > > > > >
> > > > > > > > At this point, the vote has enough PMC support to release
> > and
> > > > will
> > > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> > the
> > > > > release
> > > > > > > > should occur over the weekend.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > To: Maven Developers List
> > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > >
> > > > > > > > It's been about 5 months since an eclipse plugin release
> and
> > > we
> > > > have
> > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > >
> > > > > > > > Bug
> > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > incorrect
> > > > for
> > > > > > > ear
> > > > > > > > packaging
> > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
> when
> > > > doing
> > > > > mvn
> > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> > as
> > > > > > > > case-sensitive
> > > > > > > > * [MECLIPSE-234] - [PATCH]
> > EclipsePlugin.extractResourceDirs()
> > > > > reuses
> > > > > > > > String method argument causing maven-eclipse.xml
> > > copy-resources
> > > > > > > problems
> > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> > the
> > > > > > > > resolution:=optional directive
> > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > aren't
> > > > used
> > > > > > > in
> > > > > > > > wtp facet
> > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > Directory
> > > > > > > Server
> > > > > > > > to be built
> > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > "test"
> > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > version
> > > > > > > defined
> > > > > > > > in pom.xml
> > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> > of
> > > > 5.0 in
> > > > > a
> > > > > > > > Java 5.0 project
> > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > > projects
> > > > > in
> > > > > > > > all cases
> > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> construct
> > > > > classpath
> > > > > > > > containing dependencies with classifiers
> > > > > > > > Improvement
> > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
> JSF
> > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> make-artifacts
> > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
> of
> > > > servlet
> > > > > > > > version, jsp version, ... possible through pom
> configuration
> > > > > > > > * [MECLIPSE-286] - Ability to skip
> generated-resources/rad6
> > > > folder
> > > > > > > > creation while executing eclipse:rad
> > > > > > > > New Feature
> > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > projects
> > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
> name
> > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > >
> > > > > > > > The site has been updated:
> > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > >
> > > > > > > > Plugin is staged here:
> > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > >
> > > > > > > > Vote is open for 72hrs.
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > I could give you my word as a Spaniard.
> > > > > No good. I've known too many Spaniards.
> > > > > -- The Princess Bride
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > 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
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
RE: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I'm still not able to get any issues, even when I get 2.4 downloaded. Do
you have a proxy that might be in the way?
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 10:41 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
mvn eclipse:eclipse -P brianf-repo
I use brianf-repo profile to pickup 2.4
-D
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> See this is where I'm lost. If maven can't even find the eclipse
plugin
> to start with, how could this be a problem with 2.4 specifically? The
> comments in MECLIPSE-248 from Carlos said that if he clears his repo
and
> lets it download, it fails. That's what I did and it worked.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 10:01 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> eclispe-plugin 2.3 works fine. The problem is in the unreleased
> eclipse-2.4
>
> -Dan
>
>
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > I just tried with maven-native after clearing my repo. It correctly
> > downloads 2.3 and runs a-ok.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 9:54 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > One more fact on this, I am currently used an internal released
> version
> > of
> > eclipse plugin at
> > r541399, and it works for us. Could there be some changes in
between
> > that
> > may have
> > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> >
> > -D
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I don't think this is directly a plugin problem. I think there is
> some
> > > stray metadata floating in a repo somewhere, possibly left from a
> bad
> > > build of the unit tests, which use "test" as the version.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 1:59 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > cool, at least someone sees what i see. So this 2.4 release is a
> > nogo.
> > > -1
> > > from me.
> > >
> > > we should reopen MECLIPSE-248 as well right?
> > >
> > > Thanks
> > >
> > >
> > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > >
> > > > I wrote my problems with it in MECLIPSE-248
> > > >
> > > > * the only way to get it work so far is delete the
> > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> local
> > > > repo and install the plugin locally
> > > > * if you install without removing the folder doesn't work
> > > > * if you remove the folder and let it get downloaded doesn't
work
> > > >
> > > >
> > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > The problem reproducable with maven-scm project even with
clean
> > > local
> > > > repo.
> > > > >
> > > > > I happens on all of my known projects ( ie maven-native at
mojo
> > > > ). Note
> > > > > all projects
> > > > > involve reactor mode. Single project seems to be working
> > > > >
> > > > > Can some one confirm?
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > repository
> > > > > > entries in the project itself, presumably those repos
> contained
> > > bad
> > > > > > metadata but I wasn't able to locate it. Take a look at
> > > MECLIPSE-248,
> > > > I
> > > > > > pasted the IRC log url in there.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
SUMMARY)
> > > > > >
> > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > >
> > > > > >
> > > > > >
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > > [INFO] Failed to resolve artifact.
> > > > > >
> > > > > > GroupId: org.apache.maven.plugins
> > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > Version: test
> > > > > >
> > > > > > Reason: Unable to download the artifact from any repository
> > > > > >
> > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > >
> > > > > >
> > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > All give the same error
> > > > > >
> > > > > >
> > > > > >
> > > > > > any suggestions on how to debug this error?
> > > > > > -Dan
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > There's been a lot of discussion in this thread about the
> > > release.
> > > > Let
> > > > > > > me summarize for those trying to keep up:
> > > > > > >
> > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > Non-Binding: +1 Graham
> > > > > > >
> > > > > > > There are some transient issues with the test subsystem
used
> > by
> > > > > > eclipse
> > > > > > > that cause failures on Solaris. The issues are with the
test
> > > tools
> > > > > > > themselves, when the tests execute properly, everything
> passes
> > > and
> > > > > > thus
> > > > > > > the plugin is doing the correct thing (for the tests that
> > exist
> > > > anyway
> > > > > > > ;-) )
> > > > > > >
> > > > > > > At this point, the vote has enough PMC support to release
> and
> > > will
> > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> the
> > > > release
> > > > > > > should occur over the weekend.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > >
> > > > > > > It's been about 5 months since an eclipse plugin release
and
> > we
> > > have
> > > > > > > lots of fixes and a handful of enhancements:
> > > > > > >
> > > > > > > Bug
> > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > incorrect
> > > for
> > > > > > ear
> > > > > > > packaging
> > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
when
> > > doing
> > > > mvn
> > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> as
> > > > > > > case-sensitive
> > > > > > > * [MECLIPSE-234] - [PATCH]
> EclipsePlugin.extractResourceDirs()
> > > > reuses
> > > > > > > String method argument causing maven-eclipse.xml
> > copy-resources
> > > > > > problems
> > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> the
> > > > > > > resolution:=optional directive
> > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > aren't
> > > used
> > > > > > in
> > > > > > > wtp facet
> > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > Directory
> > > > > > Server
> > > > > > > to be built
> > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> "test"
> > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > version
> > > > > > defined
> > > > > > > in pom.xml
> > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> of
> > > 5.0 in
> > > > a
> > > > > > > Java 5.0 project
> > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > projects
> > > > in
> > > > > > > all cases
> > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
construct
> > > > classpath
> > > > > > > containing dependencies with classifiers
> > > > > > > Improvement
> > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
JSF
> > > > > > > * [MECLIPSE-267] - Resolve version ranges in
make-artifacts
> > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
of
> > > servlet
> > > > > > > version, jsp version, ... possible through pom
configuration
> > > > > > > * [MECLIPSE-286] - Ability to skip
generated-resources/rad6
> > > folder
> > > > > > > creation while executing eclipse:rad
> > > > > > > New Feature
> > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > projects
> > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
name
> > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > >
> > > > > > > The site has been updated:
> > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > >
> > > > > > > Plugin is staged here:
> > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > >
> > > > > > > Vote is open for 72hrs.
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> >
---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > I could give you my word as a Spaniard.
> > > > No good. I've known too many Spaniards.
> > > > -- The Princess Bride
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
mvn eclipse:eclipse -P brianf-repo
I use brianf-repo profile to pickup 2.4
-D
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> See this is where I'm lost. If maven can't even find the eclipse plugin
> to start with, how could this be a problem with 2.4 specifically? The
> comments in MECLIPSE-248 from Carlos said that if he clears his repo and
> lets it download, it fails. That's what I did and it worked.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 10:01 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> eclispe-plugin 2.3 works fine. The problem is in the unreleased
> eclipse-2.4
>
> -Dan
>
>
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > I just tried with maven-native after clearing my repo. It correctly
> > downloads 2.3 and runs a-ok.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 9:54 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > One more fact on this, I am currently used an internal released
> version
> > of
> > eclipse plugin at
> > r541399, and it works for us. Could there be some changes in between
> > that
> > may have
> > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> >
> > -D
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I don't think this is directly a plugin problem. I think there is
> some
> > > stray metadata floating in a repo somewhere, possibly left from a
> bad
> > > build of the unit tests, which use "test" as the version.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 1:59 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > cool, at least someone sees what i see. So this 2.4 release is a
> > nogo.
> > > -1
> > > from me.
> > >
> > > we should reopen MECLIPSE-248 as well right?
> > >
> > > Thanks
> > >
> > >
> > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > >
> > > > I wrote my problems with it in MECLIPSE-248
> > > >
> > > > * the only way to get it work so far is delete the
> > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> local
> > > > repo and install the plugin locally
> > > > * if you install without removing the folder doesn't work
> > > > * if you remove the folder and let it get downloaded doesn't work
> > > >
> > > >
> > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > The problem reproducable with maven-scm project even with clean
> > > local
> > > > repo.
> > > > >
> > > > > I happens on all of my known projects ( ie maven-native at mojo
> > > > ). Note
> > > > > all projects
> > > > > involve reactor mode. Single project seems to be working
> > > > >
> > > > > Can some one confirm?
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > repository
> > > > > > entries in the project itself, presumably those repos
> contained
> > > bad
> > > > > > metadata but I wasn't able to locate it. Take a look at
> > > MECLIPSE-248,
> > > > I
> > > > > > pasted the IRC log url in there.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > > >
> > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > >
> > > > > >
> > > > > >
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > [INFO] Failed to resolve artifact.
> > > > > >
> > > > > > GroupId: org.apache.maven.plugins
> > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > Version: test
> > > > > >
> > > > > > Reason: Unable to download the artifact from any repository
> > > > > >
> > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > >
> > > > > >
> > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > All give the same error
> > > > > >
> > > > > >
> > > > > >
> > > > > > any suggestions on how to debug this error?
> > > > > > -Dan
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > There's been a lot of discussion in this thread about the
> > > release.
> > > > Let
> > > > > > > me summarize for those trying to keep up:
> > > > > > >
> > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > Non-Binding: +1 Graham
> > > > > > >
> > > > > > > There are some transient issues with the test subsystem used
> > by
> > > > > > eclipse
> > > > > > > that cause failures on Solaris. The issues are with the test
> > > tools
> > > > > > > themselves, when the tests execute properly, everything
> passes
> > > and
> > > > > > thus
> > > > > > > the plugin is doing the correct thing (for the tests that
> > exist
> > > > anyway
> > > > > > > ;-) )
> > > > > > >
> > > > > > > At this point, the vote has enough PMC support to release
> and
> > > will
> > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> the
> > > > release
> > > > > > > should occur over the weekend.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > >
> > > > > > > It's been about 5 months since an eclipse plugin release and
> > we
> > > have
> > > > > > > lots of fixes and a handful of enhancements:
> > > > > > >
> > > > > > > Bug
> > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > incorrect
> > > for
> > > > > > ear
> > > > > > > packaging
> > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> > > doing
> > > > mvn
> > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> as
> > > > > > > case-sensitive
> > > > > > > * [MECLIPSE-234] - [PATCH]
> EclipsePlugin.extractResourceDirs()
> > > > reuses
> > > > > > > String method argument causing maven-eclipse.xml
> > copy-resources
> > > > > > problems
> > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> the
> > > > > > > resolution:=optional directive
> > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > aren't
> > > used
> > > > > > in
> > > > > > > wtp facet
> > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > Directory
> > > > > > Server
> > > > > > > to be built
> > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> "test"
> > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > version
> > > > > > defined
> > > > > > > in pom.xml
> > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> of
> > > 5.0 in
> > > > a
> > > > > > > Java 5.0 project
> > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > projects
> > > > in
> > > > > > > all cases
> > > > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > > > classpath
> > > > > > > containing dependencies with classifiers
> > > > > > > Improvement
> > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> > > servlet
> > > > > > > version, jsp version, ... possible through pom configuration
> > > > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> > > folder
> > > > > > > creation while executing eclipse:rad
> > > > > > > New Feature
> > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > projects
> > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > >
> > > > > > > The site has been updated:
> > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > >
> > > > > > > Plugin is staged here:
> > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > >
> > > > > > > Vote is open for 72hrs.
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > I could give you my word as a Spaniard.
> > > > No good. I've known too many Spaniards.
> > > > -- The Princess Bride
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Carlos Sanchez <ca...@apache.org>.
I've added MECLIPSE-295 and a test case, please give it a try
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> 2.4 works fine when I get it.
>
> -----Original Message-----
> From: carlossg@gmail.com [mailto:carlossg@gmail.com] On Behalf Of Carlos
> Sanchez
> Sent: Friday, July 06, 2007 11:58 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> set the version in the pom or run something like
> mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > See this is where I'm lost. If maven can't even find the eclipse
> plugin
> > to start with, how could this be a problem with 2.4 specifically? The
> > comments in MECLIPSE-248 from Carlos said that if he clears his repo
> and
> > lets it download, it fails. That's what I did and it worked.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 10:01 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > eclipse-2.4
> >
> > -Dan
> >
> >
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I just tried with maven-native after clearing my repo. It correctly
> > > downloads 2.3 and runs a-ok.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 9:54 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > One more fact on this, I am currently used an internal released
> > version
> > > of
> > > eclipse plugin at
> > > r541399, and it works for us. Could there be some changes in
> between
> > > that
> > > may have
> > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > >
> > > -D
> > >
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > I don't think this is directly a plugin problem. I think there is
> > some
> > > > stray metadata floating in a repo somewhere, possibly left from a
> > bad
> > > > build of the unit tests, which use "test" as the version.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > cool, at least someone sees what i see. So this 2.4 release is a
> > > nogo.
> > > > -1
> > > > from me.
> > > >
> > > > we should reopen MECLIPSE-248 as well right?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > >
> > > > > I wrote my problems with it in MECLIPSE-248
> > > > >
> > > > > * the only way to get it work so far is delete the
> > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > local
> > > > > repo and install the plugin locally
> > > > > * if you install without removing the folder doesn't work
> > > > > * if you remove the folder and let it get downloaded doesn't
> work
> > > > >
> > > > >
> > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > The problem reproducable with maven-scm project even with
> clean
> > > > local
> > > > > repo.
> > > > > >
> > > > > > I happens on all of my known projects ( ie maven-native at
> mojo
> > > > > ). Note
> > > > > > all projects
> > > > > > involve reactor mode. Single project seems to be working
> > > > > >
> > > > > > Can some one confirm?
> > > > > >
> > > > > > -D
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > > repository
> > > > > > > entries in the project itself, presumably those repos
> > contained
> > > > bad
> > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > MECLIPSE-248,
> > > > > I
> > > > > > > pasted the IRC log url in there.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> SUMMARY)
> > > > > > >
> > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > > [ERROR] BUILD ERROR
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > > [INFO] Failed to resolve artifact.
> > > > > > >
> > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > Version: test
> > > > > > >
> > > > > > > Reason: Unable to download the artifact from any repository
> > > > > > >
> > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > >
> > > > > > >
> > > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > All give the same error
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > any suggestions on how to debug this error?
> > > > > > > -Dan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > >
> > > > > > > > There's been a lot of discussion in this thread about the
> > > > release.
> > > > > Let
> > > > > > > > me summarize for those trying to keep up:
> > > > > > > >
> > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > Non-Binding: +1 Graham
> > > > > > > >
> > > > > > > > There are some transient issues with the test subsystem
> used
> > > by
> > > > > > > eclipse
> > > > > > > > that cause failures on Solaris. The issues are with the
> test
> > > > tools
> > > > > > > > themselves, when the tests execute properly, everything
> > passes
> > > > and
> > > > > > > thus
> > > > > > > > the plugin is doing the correct thing (for the tests that
> > > exist
> > > > > anyway
> > > > > > > > ;-) )
> > > > > > > >
> > > > > > > > At this point, the vote has enough PMC support to release
> > and
> > > > will
> > > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> > the
> > > > > release
> > > > > > > > should occur over the weekend.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > To: Maven Developers List
> > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > >
> > > > > > > > It's been about 5 months since an eclipse plugin release
> and
> > > we
> > > > have
> > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > >
> > > > > > > > Bug
> > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > incorrect
> > > > for
> > > > > > > ear
> > > > > > > > packaging
> > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
> when
> > > > doing
> > > > > mvn
> > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> > as
> > > > > > > > case-sensitive
> > > > > > > > * [MECLIPSE-234] - [PATCH]
> > EclipsePlugin.extractResourceDirs()
> > > > > reuses
> > > > > > > > String method argument causing maven-eclipse.xml
> > > copy-resources
> > > > > > > problems
> > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> > the
> > > > > > > > resolution:=optional directive
> > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > aren't
> > > > used
> > > > > > > in
> > > > > > > > wtp facet
> > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > Directory
> > > > > > > Server
> > > > > > > > to be built
> > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > "test"
> > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > version
> > > > > > > defined
> > > > > > > > in pom.xml
> > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> > of
> > > > 5.0 in
> > > > > a
> > > > > > > > Java 5.0 project
> > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > > projects
> > > > > in
> > > > > > > > all cases
> > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> construct
> > > > > classpath
> > > > > > > > containing dependencies with classifiers
> > > > > > > > Improvement
> > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
> JSF
> > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> make-artifacts
> > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
> of
> > > > servlet
> > > > > > > > version, jsp version, ... possible through pom
> configuration
> > > > > > > > * [MECLIPSE-286] - Ability to skip
> generated-resources/rad6
> > > > folder
> > > > > > > > creation while executing eclipse:rad
> > > > > > > > New Feature
> > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > projects
> > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
> name
> > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > >
> > > > > > > > The site has been updated:
> > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > >
> > > > > > > > Plugin is staged here:
> > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > >
> > > > > > > > Vote is open for 72hrs.
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > I could give you my word as a Spaniard.
> > > > > No good. I've known too many Spaniards.
> > > > > -- The Princess Bride
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > 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
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> 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
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
2.4 works fine when I get it.
-----Original Message-----
From: carlossg@gmail.com [mailto:carlossg@gmail.com] On Behalf Of Carlos
Sanchez
Sent: Friday, July 06, 2007 11:58 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
set the version in the pom or run something like
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> See this is where I'm lost. If maven can't even find the eclipse
plugin
> to start with, how could this be a problem with 2.4 specifically? The
> comments in MECLIPSE-248 from Carlos said that if he clears his repo
and
> lets it download, it fails. That's what I did and it worked.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 10:01 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> eclispe-plugin 2.3 works fine. The problem is in the unreleased
> eclipse-2.4
>
> -Dan
>
>
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > I just tried with maven-native after clearing my repo. It correctly
> > downloads 2.3 and runs a-ok.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 9:54 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > One more fact on this, I am currently used an internal released
> version
> > of
> > eclipse plugin at
> > r541399, and it works for us. Could there be some changes in
between
> > that
> > may have
> > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> >
> > -D
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I don't think this is directly a plugin problem. I think there is
> some
> > > stray metadata floating in a repo somewhere, possibly left from a
> bad
> > > build of the unit tests, which use "test" as the version.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 1:59 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > cool, at least someone sees what i see. So this 2.4 release is a
> > nogo.
> > > -1
> > > from me.
> > >
> > > we should reopen MECLIPSE-248 as well right?
> > >
> > > Thanks
> > >
> > >
> > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > >
> > > > I wrote my problems with it in MECLIPSE-248
> > > >
> > > > * the only way to get it work so far is delete the
> > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> local
> > > > repo and install the plugin locally
> > > > * if you install without removing the folder doesn't work
> > > > * if you remove the folder and let it get downloaded doesn't
work
> > > >
> > > >
> > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > The problem reproducable with maven-scm project even with
clean
> > > local
> > > > repo.
> > > > >
> > > > > I happens on all of my known projects ( ie maven-native at
mojo
> > > > ). Note
> > > > > all projects
> > > > > involve reactor mode. Single project seems to be working
> > > > >
> > > > > Can some one confirm?
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > repository
> > > > > > entries in the project itself, presumably those repos
> contained
> > > bad
> > > > > > metadata but I wasn't able to locate it. Take a look at
> > > MECLIPSE-248,
> > > > I
> > > > > > pasted the IRC log url in there.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
SUMMARY)
> > > > > >
> > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > >
> > > > > >
> > > > > >
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > > [INFO] Failed to resolve artifact.
> > > > > >
> > > > > > GroupId: org.apache.maven.plugins
> > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > Version: test
> > > > > >
> > > > > > Reason: Unable to download the artifact from any repository
> > > > > >
> > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > >
> > > > > >
> > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > All give the same error
> > > > > >
> > > > > >
> > > > > >
> > > > > > any suggestions on how to debug this error?
> > > > > > -Dan
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > There's been a lot of discussion in this thread about the
> > > release.
> > > > Let
> > > > > > > me summarize for those trying to keep up:
> > > > > > >
> > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > Non-Binding: +1 Graham
> > > > > > >
> > > > > > > There are some transient issues with the test subsystem
used
> > by
> > > > > > eclipse
> > > > > > > that cause failures on Solaris. The issues are with the
test
> > > tools
> > > > > > > themselves, when the tests execute properly, everything
> passes
> > > and
> > > > > > thus
> > > > > > > the plugin is doing the correct thing (for the tests that
> > exist
> > > > anyway
> > > > > > > ;-) )
> > > > > > >
> > > > > > > At this point, the vote has enough PMC support to release
> and
> > > will
> > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> the
> > > > release
> > > > > > > should occur over the weekend.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > >
> > > > > > > It's been about 5 months since an eclipse plugin release
and
> > we
> > > have
> > > > > > > lots of fixes and a handful of enhancements:
> > > > > > >
> > > > > > > Bug
> > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > incorrect
> > > for
> > > > > > ear
> > > > > > > packaging
> > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
when
> > > doing
> > > > mvn
> > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> as
> > > > > > > case-sensitive
> > > > > > > * [MECLIPSE-234] - [PATCH]
> EclipsePlugin.extractResourceDirs()
> > > > reuses
> > > > > > > String method argument causing maven-eclipse.xml
> > copy-resources
> > > > > > problems
> > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> the
> > > > > > > resolution:=optional directive
> > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > aren't
> > > used
> > > > > > in
> > > > > > > wtp facet
> > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > Directory
> > > > > > Server
> > > > > > > to be built
> > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> "test"
> > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > version
> > > > > > defined
> > > > > > > in pom.xml
> > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> of
> > > 5.0 in
> > > > a
> > > > > > > Java 5.0 project
> > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > projects
> > > > in
> > > > > > > all cases
> > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
construct
> > > > classpath
> > > > > > > containing dependencies with classifiers
> > > > > > > Improvement
> > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
JSF
> > > > > > > * [MECLIPSE-267] - Resolve version ranges in
make-artifacts
> > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
of
> > > servlet
> > > > > > > version, jsp version, ... possible through pom
configuration
> > > > > > > * [MECLIPSE-286] - Ability to skip
generated-resources/rad6
> > > folder
> > > > > > > creation while executing eclipse:rad
> > > > > > > New Feature
> > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > projects
> > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
name
> > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > >
> > > > > > > The site has been updated:
> > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > >
> > > > > > > Plugin is staged here:
> > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > >
> > > > > > > Vote is open for 72hrs.
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> >
---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > I could give you my word as a Spaniard.
> > > > No good. I've known too many Spaniards.
> > > > -- The Princess Bride
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > 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
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
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: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Ok, new snapshot deployed. You can check the differences by looking in
the jar/META-INF/maven/plugin.xml to make sure it has the correct
version now. I need to call a vote to release the plugin testing tools
where the fix is. I'll then take a look to see if any other eclipse
jiras have patches with tests etc that can be applied and restage. (the
one that can attach javadocs would be a nice grab if it's ready)
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Friday, July 06, 2007 11:08 PM
To: Maven Developers List
Subject: RE: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
Tell me about it. I finally have it resolved...standby for an updated
snapshot ;-)
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 9:03 PM
To: Maven Developers List
Subject: Re: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
brianf <---- debugger of the day :-)
-D
On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> at least you finally found the problem :(
> besides that it's also a problem with maven. It should cause an error
> when pom and plugin.xml don't match
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Despite my best efforts to deny it ;-) The eclipse 2.4 stage is bad.
> > Somehow the /WEB-INF/plugin.xml file contains "test" as the version
and
> > internally once maven loads the plugin jar, this version supersedes
the
> > requested version causing an attempt to resolve "test". I'm
suspecting
> > that during the test phase, the jar is built or modified and this
same
> > jar is eventually installed/deployed.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 12:52 PM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > 'mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -P
> > brianf-repo' works
> >
> > However if I directly set version in my pom and run
> >
> > mvn eclipse:eclipse -P brianf-repo
> >
> > the problem remains.
> >
> > -D
> >
> >
> >
> > On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
> > >
> > > set the version in the pom or run something like
> > > mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > See this is where I'm lost. If maven can't even find the eclipse
> > plugin
> > > > to start with, how could this be a problem with 2.4
specifically?
> > The
> > > > comments in MLIPSE-248 from Carlos said that if he clears his
repo
> > and
> > > > lets it download, it fails. That's what I did and it worked.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 10:01 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > > > eclipse-2.4
> > > >
> > > > -Dan
> > > >
> > > >
> > > >
> > > >
> > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > I just tried with maven-native after clearing my repo. It
> > correctly
> > > > > downloads 2.3 and runs a-ok.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > Sent: Friday, July 06, 2007 9:54 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > >
> > > > > One more fact on this, I am currently used an internal
released
> > > > version
> > > > > of
> > > > > eclipse plugin at
> > > > > r541399, and it works for us. Could there be some changes in
> > between
> > > > > that
> > > > > may have
> > > > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and
2.0.7
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > I don't think this is directly a plugin problem. I think
there
> > is
> > > > some
> > > > > > stray metadata floating in a repo somewhere, possibly left
from
> > a
> > > > bad
> > > > > > build of the unit tests, which use "test" as the version.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
SUMMARY)
> > > > > >
> > > > > > cool, at least someone sees what i see. So this 2.4 release
is
> > a
> > > > > nogo.
> > > > > > -1
> > > > > > from me.
> > > > > >
> > > > > > we should reopen MECLIPSE-248 as well right?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > > > >
> > > > > > > I wrote my problems with it in MECLIPSE-248
> > > > > > >
> > > > > > > * the only way to get it work so far is delete the
> > > > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from
the
> > > > local
> > > > > > > repo and install the plugin locally
> > > > > > > * if you install without removing the folder doesn't work
> > > > > > > * if you remove the folder and let it get downloaded
doesn't
> > work
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > > > The problem reproducable with maven-scm project even
with
> > clean
> > > > > > local
> > > > > > > repo.
> > > > > > > >
> > > > > > > > I happens on all of my known projects ( ie maven-native
at
> > mojo
> > > > > > > ). Note
> > > > > > > > all projects
> > > > > > > > involve reactor mode. Single project seems to be
working
> > > > > > > >
> > > > > > > > Can some one confirm?
> > > > > > > >
> > > > > > > > -D
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu>
wrote:
> > > > > > > > >
> > > > > > > > > Dan, I saw this on IRC the other day. It was related
to
> > some
> > > > > > > repository
> > > > > > > > > entries in the project itself, presumably those repos
> > > > contained
> > > > > > bad
> > > > > > > > > metadata but I wasn't able to locate it. Take a look
at
> > > > > > MECLIPSE-248,
> > > > > > > I
> > > > > > > > > pasted the IRC log url in there.
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > > > To: Maven Developers List
> > > > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> > SUMMARY)
> > > > > > > > >
> > > > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [INFO]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
------------------------------------------------------------------------
> > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > [INFO]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
------------------------------------------------------------------------
> > > > > > > > > [INFO] Failed to resolve artifact.
> > > > > > > > >
> > > > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > > > Version: test
> > > > > > > > >
> > > > > > > > > Reason: Unable to download the artifact from any
> > repository
> > > > > > > > >
> > > > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I am using brainf's staged plugin and both built 2.4
tag
> > and
> > > > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > > > All give the same error
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > any suggestions on how to debug this error?
> > > > > > > > > -Dan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu>
wrote:
> > > > > > > > > >
> > > > > > > > > > There's been a lot of discussion in this thread
about
> > the
> > > > > > release.
> > > > > > > Let
> > > > > > > > > > me summarize for those trying to keep up:
> > > > > > > > > >
> > > > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > > > Non-Binding: +1 Graham
> > > > > > > > > >
> > > > > > > > > > There are some transient issues with the test
subsystem
> > used
> > > > > by
> > > > > > > > > eclipse
> > > > > > > > > > that cause failures on Solaris. The issues are with
the
> > test
> > > > > > tools
> > > > > > > > > > themselves, when the tests execute properly,
everything
> > > > passes
> > > > > > and
> > > > > > > > > thus
> > > > > > > > > > the plugin is doing the correct thing (for the tests
> > that
> > > > > exist
> > > > > > > anyway
> > > > > > > > > > ;-) )
> > > > > > > > > >
> > > > > > > > > > At this point, the vote has enough PMC support to
> > release
> > > > and
> > > > > > will
> > > > > > > > > > continue for the remaining ~53hrs. Unless a veto
> > arrives,
> > > > the
> > > > > > > release
> > > > > > > > > > should occur over the weekend.
> > > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > > > To: Maven Developers List
> > > > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > > > >
> > > > > > > > > > It's been about 5 months since an eclipse plugin
release
> > and
> > > > > we
> > > > > > have
> > > > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > > > >
> > > > > > > > > > Bug
> > > > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > > > * [MECLIPSE-109] - .component wb-resource source
path
> > > > > incorrect
> > > > > > for
> > > > > > > > > ear
> > > > > > > > > > packaging
> > > > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources
jars
> > > > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet
information
> > when
> > > > > > doing
> > > > > > > mvn
> > > > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly
> > treated
> > > > as
> > > > > > > > > > case-sensitive
> > > > > > > > > > * [MECLIPSE-234] - [PATCH]
> > > > EclipsePlugin.extractResourceDirs()
> > > > > > > reuses
> > > > > > > > > > String method argument causing maven-eclipse.xml
> > > > > copy-resources
> > > > > > > > > problems
> > > > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should
> > preserve
> > > > the
> > > > > > > > > > resolution:=optional directive
> > > > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals()
> > method
> > > > > > > > > > * [MECLIPSE-241] - Compiler settings in
pluginManagement
> > > > > aren't
> > > > > > used
> > > > > > > > > in
> > > > > > > > > > wtp facet
> > > > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid
Apache
> > > > > Directory
> > > > > > > > > Server
> > > > > > > > > > to be built
> > > > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom
version
> > > > "test"
> > > > > > > > > > * [MECLIPSE-255] - WTP Settings does not use
servlet-api
> > > > > version
> > > > > > > > > defined
> > > > > > > > > > in pom.xml
> > > > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4
> > instead
> > > > of
> > > > > > 5.0 in
> > > > > > > a
> > > > > > > > > > Java 5.0 project
> > > > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > > > * [MECLIPSE-279] - PDE projects should be considered
> > java
> > > > > > projects
> > > > > > > in
> > > > > > > > > > all cases
> > > > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> > construct
> > > > > > > classpath
> > > > > > > > > > containing dependencies with classifiers
> > > > > > > > > > Improvement
> > > > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets,
like
> > JSF
> > > > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> > make-artifacts
> > > > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make
customization
> > of
> > > > > > servlet
> > > > > > > > > > version, jsp version, ... possible through pom
> > configuration
> > > > > > > > > > * [MECLIPSE-286] - Ability to skip
> > generated-resources/rad6
> > > > > > folder
> > > > > > > > > > creation while executing eclipse:rad
> > > > > > > > > > New Feature
> > > > > > > > > > * [MECLIPSE-119] - Allow custom project name for
eclipse
> > > > > > projects
> > > > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse
project
> > name
> > > > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > > > >
> > > > > > > > > > The site has been updated:
> > > > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > > > >
> > > > > > > > > > Plugin is staged here:
> > > > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > > > >
> > > > > > > > > > Vote is open for 72hrs.
> > > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > I could give you my word as a Spaniard.
> > > > > > > No good. I've known too many Spaniards.
> > > > > > > -- The Princess Bride
> > > > > > >
> > > > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > I could give you my word as a Spaniard.
> > > No good. I've known too many Spaniards.
> > > -- The Princess Bride
> > >
> > >
---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> 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: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Tell me about it. I finally have it resolved...standby for an updated
snapshot ;-)
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 9:03 PM
To: Maven Developers List
Subject: Re: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
brianf <---- debugger of the day :-)
-D
On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> at least you finally found the problem :(
> besides that it's also a problem with maven. It should cause an error
> when pom and plugin.xml don't match
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Despite my best efforts to deny it ;-) The eclipse 2.4 stage is bad.
> > Somehow the /WEB-INF/plugin.xml file contains "test" as the version
and
> > internally once maven loads the plugin jar, this version supersedes
the
> > requested version causing an attempt to resolve "test". I'm
suspecting
> > that during the test phase, the jar is built or modified and this
same
> > jar is eventually installed/deployed.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 12:52 PM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > 'mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -P
> > brianf-repo' works
> >
> > However if I directly set version in my pom and run
> >
> > mvn eclipse:eclipse -P brianf-repo
> >
> > the problem remains.
> >
> > -D
> >
> >
> >
> > On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
> > >
> > > set the version in the pom or run something like
> > > mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > See this is where I'm lost. If maven can't even find the eclipse
> > plugin
> > > > to start with, how could this be a problem with 2.4
specifically?
> > The
> > > > comments in MLIPSE-248 from Carlos said that if he clears his
repo
> > and
> > > > lets it download, it fails. That's what I did and it worked.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 10:01 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > > > eclipse-2.4
> > > >
> > > > -Dan
> > > >
> > > >
> > > >
> > > >
> > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > I just tried with maven-native after clearing my repo. It
> > correctly
> > > > > downloads 2.3 and runs a-ok.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > Sent: Friday, July 06, 2007 9:54 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > >
> > > > > One more fact on this, I am currently used an internal
released
> > > > version
> > > > > of
> > > > > eclipse plugin at
> > > > > r541399, and it works for us. Could there be some changes in
> > between
> > > > > that
> > > > > may have
> > > > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and
2.0.7
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > I don't think this is directly a plugin problem. I think
there
> > is
> > > > some
> > > > > > stray metadata floating in a repo somewhere, possibly left
from
> > a
> > > > bad
> > > > > > build of the unit tests, which use "test" as the version.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
SUMMARY)
> > > > > >
> > > > > > cool, at least someone sees what i see. So this 2.4 release
is
> > a
> > > > > nogo.
> > > > > > -1
> > > > > > from me.
> > > > > >
> > > > > > we should reopen MECLIPSE-248 as well right?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > > > >
> > > > > > > I wrote my problems with it in MECLIPSE-248
> > > > > > >
> > > > > > > * the only way to get it work so far is delete the
> > > > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from
the
> > > > local
> > > > > > > repo and install the plugin locally
> > > > > > > * if you install without removing the folder doesn't work
> > > > > > > * if you remove the folder and let it get downloaded
doesn't
> > work
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > > > The problem reproducable with maven-scm project even
with
> > clean
> > > > > > local
> > > > > > > repo.
> > > > > > > >
> > > > > > > > I happens on all of my known projects ( ie maven-native
at
> > mojo
> > > > > > > ). Note
> > > > > > > > all projects
> > > > > > > > involve reactor mode. Single project seems to be
working
> > > > > > > >
> > > > > > > > Can some one confirm?
> > > > > > > >
> > > > > > > > -D
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu>
wrote:
> > > > > > > > >
> > > > > > > > > Dan, I saw this on IRC the other day. It was related
to
> > some
> > > > > > > repository
> > > > > > > > > entries in the project itself, presumably those repos
> > > > contained
> > > > > > bad
> > > > > > > > > metadata but I wasn't able to locate it. Take a look
at
> > > > > > MECLIPSE-248,
> > > > > > > I
> > > > > > > > > pasted the IRC log url in there.
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > > > To: Maven Developers List
> > > > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> > SUMMARY)
> > > > > > > > >
> > > > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [INFO]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
------------------------------------------------------------------------
> > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > [INFO]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
------------------------------------------------------------------------
> > > > > > > > > [INFO] Failed to resolve artifact.
> > > > > > > > >
> > > > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > > > Version: test
> > > > > > > > >
> > > > > > > > > Reason: Unable to download the artifact from any
> > repository
> > > > > > > > >
> > > > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I am using brainf's staged plugin and both built 2.4
tag
> > and
> > > > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > > > All give the same error
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > any suggestions on how to debug this error?
> > > > > > > > > -Dan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu>
wrote:
> > > > > > > > > >
> > > > > > > > > > There's been a lot of discussion in this thread
about
> > the
> > > > > > release.
> > > > > > > Let
> > > > > > > > > > me summarize for those trying to keep up:
> > > > > > > > > >
> > > > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > > > Non-Binding: +1 Graham
> > > > > > > > > >
> > > > > > > > > > There are some transient issues with the test
subsystem
> > used
> > > > > by
> > > > > > > > > eclipse
> > > > > > > > > > that cause failures on Solaris. The issues are with
the
> > test
> > > > > > tools
> > > > > > > > > > themselves, when the tests execute properly,
everything
> > > > passes
> > > > > > and
> > > > > > > > > thus
> > > > > > > > > > the plugin is doing the correct thing (for the tests
> > that
> > > > > exist
> > > > > > > anyway
> > > > > > > > > > ;-) )
> > > > > > > > > >
> > > > > > > > > > At this point, the vote has enough PMC support to
> > release
> > > > and
> > > > > > will
> > > > > > > > > > continue for the remaining ~53hrs. Unless a veto
> > arrives,
> > > > the
> > > > > > > release
> > > > > > > > > > should occur over the weekend.
> > > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > > > To: Maven Developers List
> > > > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > > > >
> > > > > > > > > > It's been about 5 months since an eclipse plugin
release
> > and
> > > > > we
> > > > > > have
> > > > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > > > >
> > > > > > > > > > Bug
> > > > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > > > * [MECLIPSE-109] - .component wb-resource source
path
> > > > > incorrect
> > > > > > for
> > > > > > > > > ear
> > > > > > > > > > packaging
> > > > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources
jars
> > > > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet
information
> > when
> > > > > > doing
> > > > > > > mvn
> > > > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly
> > treated
> > > > as
> > > > > > > > > > case-sensitive
> > > > > > > > > > * [MECLIPSE-234] - [PATCH]
> > > > EclipsePlugin.extractResourceDirs()
> > > > > > > reuses
> > > > > > > > > > String method argument causing maven-eclipse.xml
> > > > > copy-resources
> > > > > > > > > problems
> > > > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should
> > preserve
> > > > the
> > > > > > > > > > resolution:=optional directive
> > > > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals()
> > method
> > > > > > > > > > * [MECLIPSE-241] - Compiler settings in
pluginManagement
> > > > > aren't
> > > > > > used
> > > > > > > > > in
> > > > > > > > > > wtp facet
> > > > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid
Apache
> > > > > Directory
> > > > > > > > > Server
> > > > > > > > > > to be built
> > > > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom
version
> > > > "test"
> > > > > > > > > > * [MECLIPSE-255] - WTP Settings does not use
servlet-api
> > > > > version
> > > > > > > > > defined
> > > > > > > > > > in pom.xml
> > > > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4
> > instead
> > > > of
> > > > > > 5.0 in
> > > > > > > a
> > > > > > > > > > Java 5.0 project
> > > > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > > > * [MECLIPSE-279] - PDE projects should be considered
> > java
> > > > > > projects
> > > > > > > in
> > > > > > > > > > all cases
> > > > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> > construct
> > > > > > > classpath
> > > > > > > > > > containing dependencies with classifiers
> > > > > > > > > > Improvement
> > > > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets,
like
> > JSF
> > > > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> > make-artifacts
> > > > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make
customization
> > of
> > > > > > servlet
> > > > > > > > > > version, jsp version, ... possible through pom
> > configuration
> > > > > > > > > > * [MECLIPSE-286] - Ability to skip
> > generated-resources/rad6
> > > > > > folder
> > > > > > > > > > creation while executing eclipse:rad
> > > > > > > > > > New Feature
> > > > > > > > > > * [MECLIPSE-119] - Allow custom project name for
eclipse
> > > > > > projects
> > > > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse
project
> > name
> > > > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > > > >
> > > > > > > > > > The site has been updated:
> > > > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > > > >
> > > > > > > > > > Plugin is staged here:
> > > > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > > > >
> > > > > > > > > > Vote is open for 72hrs.
> > > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > I could give you my word as a Spaniard.
> > > > > > > No good. I've known too many Spaniards.
> > > > > > > -- The Princess Bride
> > > > > > >
> > > > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > I could give you my word as a Spaniard.
> > > No good. I've known too many Spaniards.
> > > -- The Princess Bride
> > >
> > >
---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> 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: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
Posted by Dan Tran <da...@gmail.com>.
brianf <---- debugger of the day :-)
-D
On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> at least you finally found the problem :(
> besides that it's also a problem with maven. It should cause an error
> when pom and plugin.xml don't match
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Despite my best efforts to deny it ;-) The eclipse 2.4 stage is bad.
> > Somehow the /WEB-INF/plugin.xml file contains "test" as the version and
> > internally once maven loads the plugin jar, this version supersedes the
> > requested version causing an attempt to resolve "test". I'm suspecting
> > that during the test phase, the jar is built or modified and this same
> > jar is eventually installed/deployed.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 12:52 PM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > 'mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -P
> > brianf-repo' works
> >
> > However if I directly set version in my pom and run
> >
> > mvn eclipse:eclipse -P brianf-repo
> >
> > the problem remains.
> >
> > -D
> >
> >
> >
> > On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
> > >
> > > set the version in the pom or run something like
> > > mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > See this is where I'm lost. If maven can't even find the eclipse
> > plugin
> > > > to start with, how could this be a problem with 2.4 specifically?
> > The
> > > > comments in MLIPSE-248 from Carlos said that if he clears his repo
> > and
> > > > lets it download, it fails. That's what I did and it worked.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 10:01 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > > > eclipse-2.4
> > > >
> > > > -Dan
> > > >
> > > >
> > > >
> > > >
> > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > I just tried with maven-native after clearing my repo. It
> > correctly
> > > > > downloads 2.3 and runs a-ok.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > Sent: Friday, July 06, 2007 9:54 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > >
> > > > > One more fact on this, I am currently used an internal released
> > > > version
> > > > > of
> > > > > eclipse plugin at
> > > > > r541399, and it works for us. Could there be some changes in
> > between
> > > > > that
> > > > > may have
> > > > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > I don't think this is directly a plugin problem. I think there
> > is
> > > > some
> > > > > > stray metadata floating in a repo somewhere, possibly left from
> > a
> > > > bad
> > > > > > build of the unit tests, which use "test" as the version.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > > >
> > > > > > cool, at least someone sees what i see. So this 2.4 release is
> > a
> > > > > nogo.
> > > > > > -1
> > > > > > from me.
> > > > > >
> > > > > > we should reopen MECLIPSE-248 as well right?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > > > >
> > > > > > > I wrote my problems with it in MECLIPSE-248
> > > > > > >
> > > > > > > * the only way to get it work so far is delete the
> > > > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > > > local
> > > > > > > repo and install the plugin locally
> > > > > > > * if you install without removing the folder doesn't work
> > > > > > > * if you remove the folder and let it get downloaded doesn't
> > work
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > > > The problem reproducable with maven-scm project even with
> > clean
> > > > > > local
> > > > > > > repo.
> > > > > > > >
> > > > > > > > I happens on all of my known projects ( ie maven-native at
> > mojo
> > > > > > > ). Note
> > > > > > > > all projects
> > > > > > > > involve reactor mode. Single project seems to be working
> > > > > > > >
> > > > > > > > Can some one confirm?
> > > > > > > >
> > > > > > > > -D
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > > >
> > > > > > > > > Dan, I saw this on IRC the other day. It was related to
> > some
> > > > > > > repository
> > > > > > > > > entries in the project itself, presumably those repos
> > > > contained
> > > > > > bad
> > > > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > > > MECLIPSE-248,
> > > > > > > I
> > > > > > > > > pasted the IRC log url in there.
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > > > To: Maven Developers List
> > > > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> > SUMMARY)
> > > > > > > > >
> > > > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [INFO]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > ------------------------------------------------------------------------
> > > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > > [INFO]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > ------------------------------------------------------------------------
> > > > > > > > > [INFO] Failed to resolve artifact.
> > > > > > > > >
> > > > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > > > Version: test
> > > > > > > > >
> > > > > > > > > Reason: Unable to download the artifact from any
> > repository
> > > > > > > > >
> > > > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I am using brainf's staged plugin and both built 2.4 tag
> > and
> > > > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > > > All give the same error
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > any suggestions on how to debug this error?
> > > > > > > > > -Dan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > > > >
> > > > > > > > > > There's been a lot of discussion in this thread about
> > the
> > > > > > release.
> > > > > > > Let
> > > > > > > > > > me summarize for those trying to keep up:
> > > > > > > > > >
> > > > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > > > Non-Binding: +1 Graham
> > > > > > > > > >
> > > > > > > > > > There are some transient issues with the test subsystem
> > used
> > > > > by
> > > > > > > > > eclipse
> > > > > > > > > > that cause failures on Solaris. The issues are with the
> > test
> > > > > > tools
> > > > > > > > > > themselves, when the tests execute properly, everything
> > > > passes
> > > > > > and
> > > > > > > > > thus
> > > > > > > > > > the plugin is doing the correct thing (for the tests
> > that
> > > > > exist
> > > > > > > anyway
> > > > > > > > > > ;-) )
> > > > > > > > > >
> > > > > > > > > > At this point, the vote has enough PMC support to
> > release
> > > > and
> > > > > > will
> > > > > > > > > > continue for the remaining ~53hrs. Unless a veto
> > arrives,
> > > > the
> > > > > > > release
> > > > > > > > > > should occur over the weekend.
> > > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > > > To: Maven Developers List
> > > > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > > > >
> > > > > > > > > > It's been about 5 months since an eclipse plugin release
> > and
> > > > > we
> > > > > > have
> > > > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > > > >
> > > > > > > > > > Bug
> > > > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > > > incorrect
> > > > > > for
> > > > > > > > > ear
> > > > > > > > > > packaging
> > > > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
> > when
> > > > > > doing
> > > > > > > mvn
> > > > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly
> > treated
> > > > as
> > > > > > > > > > case-sensitive
> > > > > > > > > > * [MECLIPSE-234] - [PATCH]
> > > > EclipsePlugin.extractResourceDirs()
> > > > > > > reuses
> > > > > > > > > > String method argument causing maven-eclipse.xml
> > > > > copy-resources
> > > > > > > > > problems
> > > > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should
> > preserve
> > > > the
> > > > > > > > > > resolution:=optional directive
> > > > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals()
> > method
> > > > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > > > aren't
> > > > > > used
> > > > > > > > > in
> > > > > > > > > > wtp facet
> > > > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > > > Directory
> > > > > > > > > Server
> > > > > > > > > > to be built
> > > > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > > > "test"
> > > > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > > > version
> > > > > > > > > defined
> > > > > > > > > > in pom.xml
> > > > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4
> > instead
> > > > of
> > > > > > 5.0 in
> > > > > > > a
> > > > > > > > > > Java 5.0 project
> > > > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > > > * [MECLIPSE-279] - PDE projects should be considered
> > java
> > > > > > projects
> > > > > > > in
> > > > > > > > > > all cases
> > > > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> > construct
> > > > > > > classpath
> > > > > > > > > > containing dependencies with classifiers
> > > > > > > > > > Improvement
> > > > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
> > JSF
> > > > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> > make-artifacts
> > > > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
> > of
> > > > > > servlet
> > > > > > > > > > version, jsp version, ... possible through pom
> > configuration
> > > > > > > > > > * [MECLIPSE-286] - Ability to skip
> > generated-resources/rad6
> > > > > > folder
> > > > > > > > > > creation while executing eclipse:rad
> > > > > > > > > > New Feature
> > > > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > > > projects
> > > > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
> > name
> > > > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > > > >
> > > > > > > > > > The site has been updated:
> > > > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > > > >
> > > > > > > > > > Plugin is staged here:
> > > > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > > > >
> > > > > > > > > > Vote is open for 72hrs.
> > > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > > > > 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
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > I could give you my word as a Spaniard.
> > > > > > > No good. I've known too many Spaniards.
> > > > > > > -- The Princess Bride
> > > > > > >
> > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > I could give you my word as a Spaniard.
> > > No good. I've known too many Spaniards.
> > > -- The Princess Bride
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
Posted by Carlos Sanchez <ca...@apache.org>.
at least you finally found the problem :(
besides that it's also a problem with maven. It should cause an error
when pom and plugin.xml don't match
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Despite my best efforts to deny it ;-) The eclipse 2.4 stage is bad.
> Somehow the /WEB-INF/plugin.xml file contains "test" as the version and
> internally once maven loads the plugin jar, this version supersedes the
> requested version causing an attempt to resolve "test". I'm suspecting
> that during the test phase, the jar is built or modified and this same
> jar is eventually installed/deployed.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 12:52 PM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> 'mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -P
> brianf-repo' works
>
> However if I directly set version in my pom and run
>
> mvn eclipse:eclipse -P brianf-repo
>
> the problem remains.
>
> -D
>
>
>
> On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
> >
> > set the version in the pom or run something like
> > mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > See this is where I'm lost. If maven can't even find the eclipse
> plugin
> > > to start with, how could this be a problem with 2.4 specifically?
> The
> > > comments in MLIPSE-248 from Carlos said that if he clears his repo
> and
> > > lets it download, it fails. That's what I did and it worked.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 10:01 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > > eclipse-2.4
> > >
> > > -Dan
> > >
> > >
> > >
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > I just tried with maven-native after clearing my repo. It
> correctly
> > > > downloads 2.3 and runs a-ok.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 9:54 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > One more fact on this, I am currently used an internal released
> > > version
> > > > of
> > > > eclipse plugin at
> > > > r541399, and it works for us. Could there be some changes in
> between
> > > > that
> > > > may have
> > > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > > >
> > > > -D
> > > >
> > > >
> > > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > I don't think this is directly a plugin problem. I think there
> is
> > > some
> > > > > stray metadata floating in a repo somewhere, possibly left from
> a
> > > bad
> > > > > build of the unit tests, which use "test" as the version.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > >
> > > > > cool, at least someone sees what i see. So this 2.4 release is
> a
> > > > nogo.
> > > > > -1
> > > > > from me.
> > > > >
> > > > > we should reopen MECLIPSE-248 as well right?
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > > >
> > > > > > I wrote my problems with it in MECLIPSE-248
> > > > > >
> > > > > > * the only way to get it work so far is delete the
> > > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > > local
> > > > > > repo and install the plugin locally
> > > > > > * if you install without removing the folder doesn't work
> > > > > > * if you remove the folder and let it get downloaded doesn't
> work
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > > The problem reproducable with maven-scm project even with
> clean
> > > > > local
> > > > > > repo.
> > > > > > >
> > > > > > > I happens on all of my known projects ( ie maven-native at
> mojo
> > > > > > ). Note
> > > > > > > all projects
> > > > > > > involve reactor mode. Single project seems to be working
> > > > > > >
> > > > > > > Can some one confirm?
> > > > > > >
> > > > > > > -D
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > >
> > > > > > > > Dan, I saw this on IRC the other day. It was related to
> some
> > > > > > repository
> > > > > > > > entries in the project itself, presumably those repos
> > > contained
> > > > > bad
> > > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > > MECLIPSE-248,
> > > > > > I
> > > > > > > > pasted the IRC log url in there.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > > To: Maven Developers List
> > > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
> SUMMARY)
> > > > > > > >
> > > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > [INFO]
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> ------------------------------------------------------------------------
> > > > > > > > [ERROR] BUILD ERROR
> > > > > > > > [INFO]
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> ------------------------------------------------------------------------
> > > > > > > > [INFO] Failed to resolve artifact.
> > > > > > > >
> > > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > > Version: test
> > > > > > > >
> > > > > > > > Reason: Unable to download the artifact from any
> repository
> > > > > > > >
> > > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > > >
> > > > > > > >
> > > > > > > > I am using brainf's staged plugin and both built 2.4 tag
> and
> > > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > > All give the same error
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > any suggestions on how to debug this error?
> > > > > > > > -Dan
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > > >
> > > > > > > > > There's been a lot of discussion in this thread about
> the
> > > > > release.
> > > > > > Let
> > > > > > > > > me summarize for those trying to keep up:
> > > > > > > > >
> > > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > > Non-Binding: +1 Graham
> > > > > > > > >
> > > > > > > > > There are some transient issues with the test subsystem
> used
> > > > by
> > > > > > > > eclipse
> > > > > > > > > that cause failures on Solaris. The issues are with the
> test
> > > > > tools
> > > > > > > > > themselves, when the tests execute properly, everything
> > > passes
> > > > > and
> > > > > > > > thus
> > > > > > > > > the plugin is doing the correct thing (for the tests
> that
> > > > exist
> > > > > > anyway
> > > > > > > > > ;-) )
> > > > > > > > >
> > > > > > > > > At this point, the vote has enough PMC support to
> release
> > > and
> > > > > will
> > > > > > > > > continue for the remaining ~53hrs. Unless a veto
> arrives,
> > > the
> > > > > > release
> > > > > > > > > should occur over the weekend.
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > > To: Maven Developers List
> > > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > > >
> > > > > > > > > It's been about 5 months since an eclipse plugin release
> and
> > > > we
> > > > > have
> > > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > > >
> > > > > > > > > Bug
> > > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > > incorrect
> > > > > for
> > > > > > > > ear
> > > > > > > > > packaging
> > > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
> when
> > > > > doing
> > > > > > mvn
> > > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly
> treated
> > > as
> > > > > > > > > case-sensitive
> > > > > > > > > * [MECLIPSE-234] - [PATCH]
> > > EclipsePlugin.extractResourceDirs()
> > > > > > reuses
> > > > > > > > > String method argument causing maven-eclipse.xml
> > > > copy-resources
> > > > > > > > problems
> > > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should
> preserve
> > > the
> > > > > > > > > resolution:=optional directive
> > > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals()
> method
> > > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > > aren't
> > > > > used
> > > > > > > > in
> > > > > > > > > wtp facet
> > > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > > Directory
> > > > > > > > Server
> > > > > > > > > to be built
> > > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > > "test"
> > > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > > version
> > > > > > > > defined
> > > > > > > > > in pom.xml
> > > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4
> instead
> > > of
> > > > > 5.0 in
> > > > > > a
> > > > > > > > > Java 5.0 project
> > > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > > * [MECLIPSE-279] - PDE projects should be considered
> java
> > > > > projects
> > > > > > in
> > > > > > > > > all cases
> > > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
> construct
> > > > > > classpath
> > > > > > > > > containing dependencies with classifiers
> > > > > > > > > Improvement
> > > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
> JSF
> > > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
> make-artifacts
> > > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
> of
> > > > > servlet
> > > > > > > > > version, jsp version, ... possible through pom
> configuration
> > > > > > > > > * [MECLIPSE-286] - Ability to skip
> generated-resources/rad6
> > > > > folder
> > > > > > > > > creation while executing eclipse:rad
> > > > > > > > > New Feature
> > > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > > projects
> > > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
> name
> > > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > > >
> > > > > > > > > The site has been updated:
> > > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > > >
> > > > > > > > > Plugin is staged here:
> > > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > > >
> > > > > > > > > Vote is open for 72hrs.
> > > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > > > > 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
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > I could give you my word as a Spaniard.
> > > > > > No good. I've known too many Spaniards.
> > > > > > -- The Princess Bride
> > > > > >
> > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > 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
> > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
CANCELLED: [VOTE] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Despite my best efforts to deny it ;-) The eclipse 2.4 stage is bad.
Somehow the /WEB-INF/plugin.xml file contains "test" as the version and
internally once maven loads the plugin jar, this version supersedes the
requested version causing an attempt to resolve "test". I'm suspecting
that during the test phase, the jar is built or modified and this same
jar is eventually installed/deployed.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 12:52 PM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
'mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -P
brianf-repo' works
However if I directly set version in my pom and run
mvn eclipse:eclipse -P brianf-repo
the problem remains.
-D
On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> set the version in the pom or run something like
> mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > See this is where I'm lost. If maven can't even find the eclipse
plugin
> > to start with, how could this be a problem with 2.4 specifically?
The
> > comments in MLIPSE-248 from Carlos said that if he clears his repo
and
> > lets it download, it fails. That's what I did and it worked.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 10:01 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > eclipse-2.4
> >
> > -Dan
> >
> >
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I just tried with maven-native after clearing my repo. It
correctly
> > > downloads 2.3 and runs a-ok.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 9:54 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > One more fact on this, I am currently used an internal released
> > version
> > > of
> > > eclipse plugin at
> > > r541399, and it works for us. Could there be some changes in
between
> > > that
> > > may have
> > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > >
> > > -D
> > >
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > I don't think this is directly a plugin problem. I think there
is
> > some
> > > > stray metadata floating in a repo somewhere, possibly left from
a
> > bad
> > > > build of the unit tests, which use "test" as the version.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > cool, at least someone sees what i see. So this 2.4 release is
a
> > > nogo.
> > > > -1
> > > > from me.
> > > >
> > > > we should reopen MECLIPSE-248 as well right?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > >
> > > > > I wrote my problems with it in MECLIPSE-248
> > > > >
> > > > > * the only way to get it work so far is delete the
> > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > local
> > > > > repo and install the plugin locally
> > > > > * if you install without removing the folder doesn't work
> > > > > * if you remove the folder and let it get downloaded doesn't
work
> > > > >
> > > > >
> > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > The problem reproducable with maven-scm project even with
clean
> > > > local
> > > > > repo.
> > > > > >
> > > > > > I happens on all of my known projects ( ie maven-native at
mojo
> > > > > ). Note
> > > > > > all projects
> > > > > > involve reactor mode. Single project seems to be working
> > > > > >
> > > > > > Can some one confirm?
> > > > > >
> > > > > > -D
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > Dan, I saw this on IRC the other day. It was related to
some
> > > > > repository
> > > > > > > entries in the project itself, presumably those repos
> > contained
> > > > bad
> > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > MECLIPSE-248,
> > > > > I
> > > > > > > pasted the IRC log url in there.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT
SUMMARY)
> > > > > > >
> > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
------------------------------------------------------------------------
> > > > > > > [ERROR] BUILD ERROR
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> >
------------------------------------------------------------------------
> > > > > > > [INFO] Failed to resolve artifact.
> > > > > > >
> > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > Version: test
> > > > > > >
> > > > > > > Reason: Unable to download the artifact from any
repository
> > > > > > >
> > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > >
> > > > > > >
> > > > > > > I am using brainf's staged plugin and both built 2.4 tag
and
> > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > All give the same error
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > any suggestions on how to debug this error?
> > > > > > > -Dan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > >
> > > > > > > > There's been a lot of discussion in this thread about
the
> > > > release.
> > > > > Let
> > > > > > > > me summarize for those trying to keep up:
> > > > > > > >
> > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > Non-Binding: +1 Graham
> > > > > > > >
> > > > > > > > There are some transient issues with the test subsystem
used
> > > by
> > > > > > > eclipse
> > > > > > > > that cause failures on Solaris. The issues are with the
test
> > > > tools
> > > > > > > > themselves, when the tests execute properly, everything
> > passes
> > > > and
> > > > > > > thus
> > > > > > > > the plugin is doing the correct thing (for the tests
that
> > > exist
> > > > > anyway
> > > > > > > > ;-) )
> > > > > > > >
> > > > > > > > At this point, the vote has enough PMC support to
release
> > and
> > > > will
> > > > > > > > continue for the remaining ~53hrs. Unless a veto
arrives,
> > the
> > > > > release
> > > > > > > > should occur over the weekend.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > To: Maven Developers List
> > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > >
> > > > > > > > It's been about 5 months since an eclipse plugin release
and
> > > we
> > > > have
> > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > >
> > > > > > > > Bug
> > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > incorrect
> > > > for
> > > > > > > ear
> > > > > > > > packaging
> > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information
when
> > > > doing
> > > > > mvn
> > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly
treated
> > as
> > > > > > > > case-sensitive
> > > > > > > > * [MECLIPSE-234] - [PATCH]
> > EclipsePlugin.extractResourceDirs()
> > > > > reuses
> > > > > > > > String method argument causing maven-eclipse.xml
> > > copy-resources
> > > > > > > problems
> > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should
preserve
> > the
> > > > > > > > resolution:=optional directive
> > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals()
method
> > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > aren't
> > > > used
> > > > > > > in
> > > > > > > > wtp facet
> > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > Directory
> > > > > > > Server
> > > > > > > > to be built
> > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > "test"
> > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > version
> > > > > > > defined
> > > > > > > > in pom.xml
> > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4
instead
> > of
> > > > 5.0 in
> > > > > a
> > > > > > > > Java 5.0 project
> > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > * [MECLIPSE-279] - PDE projects should be considered
java
> > > > projects
> > > > > in
> > > > > > > > all cases
> > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly
construct
> > > > > classpath
> > > > > > > > containing dependencies with classifiers
> > > > > > > > Improvement
> > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like
JSF
> > > > > > > > * [MECLIPSE-267] - Resolve version ranges in
make-artifacts
> > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization
of
> > > > servlet
> > > > > > > > version, jsp version, ... possible through pom
configuration
> > > > > > > > * [MECLIPSE-286] - Ability to skip
generated-resources/rad6
> > > > folder
> > > > > > > > creation while executing eclipse:rad
> > > > > > > > New Feature
> > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > projects
> > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project
name
> > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > >
> > > > > > > > The site has been updated:
> > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > >
> > > > > > > > Plugin is staged here:
> > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > >
> > > > > > > > Vote is open for 72hrs.
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > >
---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > I could give you my word as a Spaniard.
> > > > > No good. I've known too many Spaniards.
> > > > > -- The Princess Bride
> > > > >
> > > > >
> > >
---------------------------------------------------------------------
> > > > > 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
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
'mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -P
brianf-repo' works
However if I directly set version in my pom and run
mvn eclipse:eclipse -P brianf-repo
the problem remains.
-D
On 7/6/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> set the version in the pom or run something like
> mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > See this is where I'm lost. If maven can't even find the eclipse plugin
> > to start with, how could this be a problem with 2.4 specifically? The
> > comments in MLIPSE-248 from Carlos said that if he clears his repo and
> > lets it download, it fails. That's what I did and it worked.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 10:01 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > eclispe-plugin 2.3 works fine. The problem is in the unreleased
> > eclipse-2.4
> >
> > -Dan
> >
> >
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I just tried with maven-native after clearing my repo. It correctly
> > > downloads 2.3 and runs a-ok.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 9:54 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > One more fact on this, I am currently used an internal released
> > version
> > > of
> > > eclipse plugin at
> > > r541399, and it works for us. Could there be some changes in between
> > > that
> > > may have
> > > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> > >
> > > -D
> > >
> > >
> > > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > I don't think this is directly a plugin problem. I think there is
> > some
> > > > stray metadata floating in a repo somewhere, possibly left from a
> > bad
> > > > build of the unit tests, which use "test" as the version.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Friday, July 06, 2007 1:59 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > cool, at least someone sees what i see. So this 2.4 release is a
> > > nogo.
> > > > -1
> > > > from me.
> > > >
> > > > we should reopen MECLIPSE-248 as well right?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > > >
> > > > > I wrote my problems with it in MECLIPSE-248
> > > > >
> > > > > * the only way to get it work so far is delete the
> > > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> > local
> > > > > repo and install the plugin locally
> > > > > * if you install without removing the folder doesn't work
> > > > > * if you remove the folder and let it get downloaded doesn't work
> > > > >
> > > > >
> > > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > > The problem reproducable with maven-scm project even with clean
> > > > local
> > > > > repo.
> > > > > >
> > > > > > I happens on all of my known projects ( ie maven-native at mojo
> > > > > ). Note
> > > > > > all projects
> > > > > > involve reactor mode. Single project seems to be working
> > > > > >
> > > > > > Can some one confirm?
> > > > > >
> > > > > > -D
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > > repository
> > > > > > > entries in the project itself, presumably those repos
> > contained
> > > > bad
> > > > > > > metadata but I wasn't able to locate it. Take a look at
> > > > MECLIPSE-248,
> > > > > I
> > > > > > > pasted the IRC log url in there.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > > > >
> > > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> > ------------------------------------------------------------------------
> > > > > > > [ERROR] BUILD ERROR
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > > >
> > >
> > ------------------------------------------------------------------------
> > > > > > > [INFO] Failed to resolve artifact.
> > > > > > >
> > > > > > > GroupId: org.apache.maven.plugins
> > > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > > Version: test
> > > > > > >
> > > > > > > Reason: Unable to download the artifact from any repository
> > > > > > >
> > > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > > >
> > > > > > >
> > > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > > All give the same error
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > any suggestions on how to debug this error?
> > > > > > > -Dan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > > >
> > > > > > > > There's been a lot of discussion in this thread about the
> > > > release.
> > > > > Let
> > > > > > > > me summarize for those trying to keep up:
> > > > > > > >
> > > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > > Non-Binding: +1 Graham
> > > > > > > >
> > > > > > > > There are some transient issues with the test subsystem used
> > > by
> > > > > > > eclipse
> > > > > > > > that cause failures on Solaris. The issues are with the test
> > > > tools
> > > > > > > > themselves, when the tests execute properly, everything
> > passes
> > > > and
> > > > > > > thus
> > > > > > > > the plugin is doing the correct thing (for the tests that
> > > exist
> > > > > anyway
> > > > > > > > ;-) )
> > > > > > > >
> > > > > > > > At this point, the vote has enough PMC support to release
> > and
> > > > will
> > > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> > the
> > > > > release
> > > > > > > > should occur over the weekend.
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > > To: Maven Developers List
> > > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > > >
> > > > > > > > It's been about 5 months since an eclipse plugin release and
> > > we
> > > > have
> > > > > > > > lots of fixes and a handful of enhancements:
> > > > > > > >
> > > > > > > > Bug
> > > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > > incorrect
> > > > for
> > > > > > > ear
> > > > > > > > packaging
> > > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> > > > doing
> > > > > mvn
> > > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> > as
> > > > > > > > case-sensitive
> > > > > > > > * [MECLIPSE-234] - [PATCH]
> > EclipsePlugin.extractResourceDirs()
> > > > > reuses
> > > > > > > > String method argument causing maven-eclipse.xml
> > > copy-resources
> > > > > > > problems
> > > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> > the
> > > > > > > > resolution:=optional directive
> > > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > > aren't
> > > > used
> > > > > > > in
> > > > > > > > wtp facet
> > > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > > Directory
> > > > > > > Server
> > > > > > > > to be built
> > > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> > "test"
> > > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > > version
> > > > > > > defined
> > > > > > > > in pom.xml
> > > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> > of
> > > > 5.0 in
> > > > > a
> > > > > > > > Java 5.0 project
> > > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > > projects
> > > > > in
> > > > > > > > all cases
> > > > > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > > > > classpath
> > > > > > > > containing dependencies with classifiers
> > > > > > > > Improvement
> > > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> > > > servlet
> > > > > > > > version, jsp version, ... possible through pom configuration
> > > > > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> > > > folder
> > > > > > > > creation while executing eclipse:rad
> > > > > > > > New Feature
> > > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > > projects
> > > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > > >
> > > > > > > > The site has been updated:
> > > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > > >
> > > > > > > > Plugin is staged here:
> > > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > > >
> > > > > > > > Vote is open for 72hrs.
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > I could give you my word as a Spaniard.
> > > > > No good. I've known too many Spaniards.
> > > > > -- The Princess Bride
> > > > >
> > > > >
> > > ---------------------------------------------------------------------
> > > > > 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
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Carlos Sanchez <ca...@apache.org>.
set the version in the pom or run something like
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> See this is where I'm lost. If maven can't even find the eclipse plugin
> to start with, how could this be a problem with 2.4 specifically? The
> comments in MECLIPSE-248 from Carlos said that if he clears his repo and
> lets it download, it fails. That's what I did and it worked.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 10:01 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> eclispe-plugin 2.3 works fine. The problem is in the unreleased
> eclipse-2.4
>
> -Dan
>
>
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > I just tried with maven-native after clearing my repo. It correctly
> > downloads 2.3 and runs a-ok.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 9:54 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > One more fact on this, I am currently used an internal released
> version
> > of
> > eclipse plugin at
> > r541399, and it works for us. Could there be some changes in between
> > that
> > may have
> > trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
> >
> > -D
> >
> >
> > On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > I don't think this is directly a plugin problem. I think there is
> some
> > > stray metadata floating in a repo somewhere, possibly left from a
> bad
> > > build of the unit tests, which use "test" as the version.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Friday, July 06, 2007 1:59 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > cool, at least someone sees what i see. So this 2.4 release is a
> > nogo.
> > > -1
> > > from me.
> > >
> > > we should reopen MECLIPSE-248 as well right?
> > >
> > > Thanks
> > >
> > >
> > > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > > >
> > > > I wrote my problems with it in MECLIPSE-248
> > > >
> > > > * the only way to get it work so far is delete the
> > > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
> local
> > > > repo and install the plugin locally
> > > > * if you install without removing the folder doesn't work
> > > > * if you remove the folder and let it get downloaded doesn't work
> > > >
> > > >
> > > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > > The problem reproducable with maven-scm project even with clean
> > > local
> > > > repo.
> > > > >
> > > > > I happens on all of my known projects ( ie maven-native at mojo
> > > > ). Note
> > > > > all projects
> > > > > involve reactor mode. Single project seems to be working
> > > > >
> > > > > Can some one confirm?
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > Dan, I saw this on IRC the other day. It was related to some
> > > > repository
> > > > > > entries in the project itself, presumably those repos
> contained
> > > bad
> > > > > > metadata but I wasn't able to locate it. Take a look at
> > > MECLIPSE-248,
> > > > I
> > > > > > pasted the IRC log url in there.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > > >
> > > > > > I got this error with fresh mvn eclipse:eclipse
> > > > > >
> > > > > >
> > > > > >
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > [ERROR] BUILD ERROR
> > > > > > [INFO]
> > > > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > > [INFO] Failed to resolve artifact.
> > > > > >
> > > > > > GroupId: org.apache.maven.plugins
> > > > > > ArtifactId: maven-eclipse-plugin
> > > > > > Version: test
> > > > > >
> > > > > > Reason: Unable to download the artifact from any repository
> > > > > >
> > > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > > >
> > > > > >
> > > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > > All give the same error
> > > > > >
> > > > > >
> > > > > >
> > > > > > any suggestions on how to debug this error?
> > > > > > -Dan
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > > >
> > > > > > > There's been a lot of discussion in this thread about the
> > > release.
> > > > Let
> > > > > > > me summarize for those trying to keep up:
> > > > > > >
> > > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > > Non-Binding: +1 Graham
> > > > > > >
> > > > > > > There are some transient issues with the test subsystem used
> > by
> > > > > > eclipse
> > > > > > > that cause failures on Solaris. The issues are with the test
> > > tools
> > > > > > > themselves, when the tests execute properly, everything
> passes
> > > and
> > > > > > thus
> > > > > > > the plugin is doing the correct thing (for the tests that
> > exist
> > > > anyway
> > > > > > > ;-) )
> > > > > > >
> > > > > > > At this point, the vote has enough PMC support to release
> and
> > > will
> > > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
> the
> > > > release
> > > > > > > should occur over the weekend.
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > > To: Maven Developers List
> > > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > > >
> > > > > > > It's been about 5 months since an eclipse plugin release and
> > we
> > > have
> > > > > > > lots of fixes and a handful of enhancements:
> > > > > > >
> > > > > > > Bug
> > > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > > javax.servlet:servlet-api:2.3
> > > > > > > * [MECLIPSE-109] - .component wb-resource source path
> > incorrect
> > > for
> > > > > > ear
> > > > > > > packaging
> > > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> > > doing
> > > > mvn
> > > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
> as
> > > > > > > case-sensitive
> > > > > > > * [MECLIPSE-234] - [PATCH]
> EclipsePlugin.extractResourceDirs()
> > > > reuses
> > > > > > > String method argument causing maven-eclipse.xml
> > copy-resources
> > > > > > problems
> > > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
> the
> > > > > > > resolution:=optional directive
> > > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> > aren't
> > > used
> > > > > > in
> > > > > > > wtp facet
> > > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> > Directory
> > > > > > Server
> > > > > > > to be built
> > > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
> "test"
> > > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> > version
> > > > > > defined
> > > > > > > in pom.xml
> > > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
> of
> > > 5.0 in
> > > > a
> > > > > > > Java 5.0 project
> > > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > > projects
> > > > in
> > > > > > > all cases
> > > > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > > > classpath
> > > > > > > containing dependencies with classifiers
> > > > > > > Improvement
> > > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> > > servlet
> > > > > > > version, jsp version, ... possible through pom configuration
> > > > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> > > folder
> > > > > > > creation while executing eclipse:rad
> > > > > > > New Feature
> > > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > > projects
> > > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > > >
> > > > > > > The site has been updated:
> > > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > > >
> > > > > > > Plugin is staged here:
> > > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > > >
> > > > > > > Vote is open for 72hrs.
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > I could give you my word as a Spaniard.
> > > > No good. I've known too many Spaniards.
> > > > -- The Princess Bride
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > 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
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
See this is where I'm lost. If maven can't even find the eclipse plugin
to start with, how could this be a problem with 2.4 specifically? The
comments in MECLIPSE-248 from Carlos said that if he clears his repo and
lets it download, it fails. That's what I did and it worked.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 10:01 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
eclispe-plugin 2.3 works fine. The problem is in the unreleased
eclipse-2.4
-Dan
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> I just tried with maven-native after clearing my repo. It correctly
> downloads 2.3 and runs a-ok.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 9:54 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> One more fact on this, I am currently used an internal released
version
> of
> eclipse plugin at
> r541399, and it works for us. Could there be some changes in between
> that
> may have
> trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
>
> -D
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > I don't think this is directly a plugin problem. I think there is
some
> > stray metadata floating in a repo somewhere, possibly left from a
bad
> > build of the unit tests, which use "test" as the version.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 1:59 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > cool, at least someone sees what i see. So this 2.4 release is a
> nogo.
> > -1
> > from me.
> >
> > we should reopen MECLIPSE-248 as well right?
> >
> > Thanks
> >
> >
> > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > >
> > > I wrote my problems with it in MECLIPSE-248
> > >
> > > * the only way to get it work so far is delete the
> > > org/apache/maven/plugins/maven-eclipse-plugin folder from the
local
> > > repo and install the plugin locally
> > > * if you install without removing the folder doesn't work
> > > * if you remove the folder and let it get downloaded doesn't work
> > >
> > >
> > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > The problem reproducable with maven-scm project even with clean
> > local
> > > repo.
> > > >
> > > > I happens on all of my known projects ( ie maven-native at mojo
> > > ). Note
> > > > all projects
> > > > involve reactor mode. Single project seems to be working
> > > >
> > > > Can some one confirm?
> > > >
> > > > -D
> > > >
> > > >
> > > >
> > > >
> > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > Dan, I saw this on IRC the other day. It was related to some
> > > repository
> > > > > entries in the project itself, presumably those repos
contained
> > bad
> > > > > metadata but I wasn't able to locate it. Take a look at
> > MECLIPSE-248,
> > > I
> > > > > pasted the IRC log url in there.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > >
> > > > > I got this error with fresh mvn eclipse:eclipse
> > > > >
> > > > >
> > > > >
> > > > > [INFO]
> > > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO]
> > > > >
> > >
> >
>
------------------------------------------------------------------------
> > > > > [INFO] Failed to resolve artifact.
> > > > >
> > > > > GroupId: org.apache.maven.plugins
> > > > > ArtifactId: maven-eclipse-plugin
> > > > > Version: test
> > > > >
> > > > > Reason: Unable to download the artifact from any repository
> > > > >
> > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > >
> > > > >
> > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > All give the same error
> > > > >
> > > > >
> > > > >
> > > > > any suggestions on how to debug this error?
> > > > > -Dan
> > > > >
> > > > >
> > > > >
> > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > There's been a lot of discussion in this thread about the
> > release.
> > > Let
> > > > > > me summarize for those trying to keep up:
> > > > > >
> > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > Non-Binding: +1 Graham
> > > > > >
> > > > > > There are some transient issues with the test subsystem used
> by
> > > > > eclipse
> > > > > > that cause failures on Solaris. The issues are with the test
> > tools
> > > > > > themselves, when the tests execute properly, everything
passes
> > and
> > > > > thus
> > > > > > the plugin is doing the correct thing (for the tests that
> exist
> > > anyway
> > > > > > ;-) )
> > > > > >
> > > > > > At this point, the vote has enough PMC support to release
and
> > will
> > > > > > continue for the remaining ~53hrs. Unless a veto arrives,
the
> > > release
> > > > > > should occur over the weekend.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > To: Maven Developers List
> > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > >
> > > > > > It's been about 5 months since an eclipse plugin release and
> we
> > have
> > > > > > lots of fixes and a handful of enhancements:
> > > > > >
> > > > > > Bug
> > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > javax.servlet:servlet-api:2.3
> > > > > > * [MECLIPSE-109] - .component wb-resource source path
> incorrect
> > for
> > > > > ear
> > > > > > packaging
> > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> > doing
> > > mvn
> > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated
as
> > > > > > case-sensitive
> > > > > > * [MECLIPSE-234] - [PATCH]
EclipsePlugin.extractResourceDirs()
> > > reuses
> > > > > > String method argument causing maven-eclipse.xml
> copy-resources
> > > > > problems
> > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve
the
> > > > > > resolution:=optional directive
> > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> aren't
> > used
> > > > > in
> > > > > > wtp facet
> > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> Directory
> > > > > Server
> > > > > > to be built
> > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version
"test"
> > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> version
> > > > > defined
> > > > > > in pom.xml
> > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead
of
> > 5.0 in
> > > a
> > > > > > Java 5.0 project
> > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > projects
> > > in
> > > > > > all cases
> > > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > > classpath
> > > > > > containing dependencies with classifiers
> > > > > > Improvement
> > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> > servlet
> > > > > > version, jsp version, ... possible through pom configuration
> > > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> > folder
> > > > > > creation while executing eclipse:rad
> > > > > > New Feature
> > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > projects
> > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > >
> > > > > > The site has been updated:
> > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > >
> > > > > > Plugin is staged here:
> > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > >
> > > > > > Vote is open for 72hrs.
> > > > > >
> > > > > > +1
> > > > > >
> > > > > >
> > > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > I could give you my word as a Spaniard.
> > > No good. I've known too many Spaniards.
> > > -- The Princess Bride
> > >
> > >
> ---------------------------------------------------------------------
> > > 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
eclispe-plugin 2.3 works fine. The problem is in the unreleased eclipse-2.4
-Dan
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> I just tried with maven-native after clearing my repo. It correctly
> downloads 2.3 and runs a-ok.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 9:54 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> One more fact on this, I am currently used an internal released version
> of
> eclipse plugin at
> r541399, and it works for us. Could there be some changes in between
> that
> may have
> trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
>
> -D
>
>
> On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > I don't think this is directly a plugin problem. I think there is some
> > stray metadata floating in a repo somewhere, possibly left from a bad
> > build of the unit tests, which use "test" as the version.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Friday, July 06, 2007 1:59 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > cool, at least someone sees what i see. So this 2.4 release is a
> nogo.
> > -1
> > from me.
> >
> > we should reopen MECLIPSE-248 as well right?
> >
> > Thanks
> >
> >
> > On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> > >
> > > I wrote my problems with it in MECLIPSE-248
> > >
> > > * the only way to get it work so far is delete the
> > > org/apache/maven/plugins/maven-eclipse-plugin folder from the local
> > > repo and install the plugin locally
> > > * if you install without removing the folder doesn't work
> > > * if you remove the folder and let it get downloaded doesn't work
> > >
> > >
> > > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > > The problem reproducable with maven-scm project even with clean
> > local
> > > repo.
> > > >
> > > > I happens on all of my known projects ( ie maven-native at mojo
> > > ). Note
> > > > all projects
> > > > involve reactor mode. Single project seems to be working
> > > >
> > > > Can some one confirm?
> > > >
> > > > -D
> > > >
> > > >
> > > >
> > > >
> > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > Dan, I saw this on IRC the other day. It was related to some
> > > repository
> > > > > entries in the project itself, presumably those repos contained
> > bad
> > > > > metadata but I wasn't able to locate it. Take a look at
> > MECLIPSE-248,
> > > I
> > > > > pasted the IRC log url in there.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > > >
> > > > > I got this error with fresh mvn eclipse:eclipse
> > > > >
> > > > >
> > > > >
> > > > > [INFO]
> > > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > [ERROR] BUILD ERROR
> > > > > [INFO]
> > > > >
> > >
> >
> ------------------------------------------------------------------------
> > > > > [INFO] Failed to resolve artifact.
> > > > >
> > > > > GroupId: org.apache.maven.plugins
> > > > > ArtifactId: maven-eclipse-plugin
> > > > > Version: test
> > > > >
> > > > > Reason: Unable to download the artifact from any repository
> > > > >
> > > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > > >
> > > > >
> > > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > > All give the same error
> > > > >
> > > > >
> > > > >
> > > > > any suggestions on how to debug this error?
> > > > > -Dan
> > > > >
> > > > >
> > > > >
> > > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > > >
> > > > > > There's been a lot of discussion in this thread about the
> > release.
> > > Let
> > > > > > me summarize for those trying to keep up:
> > > > > >
> > > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > > Non-Binding: +1 Graham
> > > > > >
> > > > > > There are some transient issues with the test subsystem used
> by
> > > > > eclipse
> > > > > > that cause failures on Solaris. The issues are with the test
> > tools
> > > > > > themselves, when the tests execute properly, everything passes
> > and
> > > > > thus
> > > > > > the plugin is doing the correct thing (for the tests that
> exist
> > > anyway
> > > > > > ;-) )
> > > > > >
> > > > > > At this point, the vote has enough PMC support to release and
> > will
> > > > > > continue for the remaining ~53hrs. Unless a veto arrives, the
> > > release
> > > > > > should occur over the weekend.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > > To: Maven Developers List
> > > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > > >
> > > > > > It's been about 5 months since an eclipse plugin release and
> we
> > have
> > > > > > lots of fixes and a handful of enhancements:
> > > > > >
> > > > > > Bug
> > > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > > javax.servlet:servlet-api:2.3
> > > > > > * [MECLIPSE-109] - .component wb-resource source path
> incorrect
> > for
> > > > > ear
> > > > > > packaging
> > > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> > doing
> > > mvn
> > > > > > eclipse:eclipse for war and ejb projects.
> > > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > > > > case-sensitive
> > > > > > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
> > > reuses
> > > > > > String method argument causing maven-eclipse.xml
> copy-resources
> > > > > problems
> > > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > > > > resolution:=optional directive
> > > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
> aren't
> > used
> > > > > in
> > > > > > wtp facet
> > > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
> Directory
> > > > > Server
> > > > > > to be built
> > > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
> version
> > > > > defined
> > > > > > in pom.xml
> > > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of
> > 5.0 in
> > > a
> > > > > > Java 5.0 project
> > > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > > * [MECLIPSE-279] - PDE projects should be considered java
> > projects
> > > in
> > > > > > all cases
> > > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > > classpath
> > > > > > containing dependencies with classifiers
> > > > > > Improvement
> > > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> > servlet
> > > > > > version, jsp version, ... possible through pom configuration
> > > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> > folder
> > > > > > creation while executing eclipse:rad
> > > > > > New Feature
> > > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> > projects
> > > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > > * [MECLIPSE-271] - Ability to skip
> > > > > >
> > > > > > The site has been updated:
> > > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > > >
> > > > > > Plugin is staged here:
> > > > > > http://people.apache.org/~brianf/staging-repository/
> > > > > >
> > > > > > Vote is open for 72hrs.
> > > > > >
> > > > > > +1
> > > > > >
> > > > > >
> > > > > >
> > >
> ---------------------------------------------------------------------
> > > > > > 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
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > I could give you my word as a Spaniard.
> > > No good. I've known too many Spaniards.
> > > -- The Princess Bride
> > >
> > >
> ---------------------------------------------------------------------
> > > 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I just tried with maven-native after clearing my repo. It correctly
downloads 2.3 and runs a-ok.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 9:54 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
One more fact on this, I am currently used an internal released version
of
eclipse plugin at
r541399, and it works for us. Could there be some changes in between
that
may have
trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
-D
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> I don't think this is directly a plugin problem. I think there is some
> stray metadata floating in a repo somewhere, possibly left from a bad
> build of the unit tests, which use "test" as the version.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 1:59 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> cool, at least someone sees what i see. So this 2.4 release is a
nogo.
> -1
> from me.
>
> we should reopen MECLIPSE-248 as well right?
>
> Thanks
>
>
> On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> >
> > I wrote my problems with it in MECLIPSE-248
> >
> > * the only way to get it work so far is delete the
> > org/apache/maven/plugins/maven-eclipse-plugin folder from the local
> > repo and install the plugin locally
> > * if you install without removing the folder doesn't work
> > * if you remove the folder and let it get downloaded doesn't work
> >
> >
> > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > The problem reproducable with maven-scm project even with clean
> local
> > repo.
> > >
> > > I happens on all of my known projects ( ie maven-native at mojo
> > ). Note
> > > all projects
> > > involve reactor mode. Single project seems to be working
> > >
> > > Can some one confirm?
> > >
> > > -D
> > >
> > >
> > >
> > >
> > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > Dan, I saw this on IRC the other day. It was related to some
> > repository
> > > > entries in the project itself, presumably those repos contained
> bad
> > > > metadata but I wasn't able to locate it. Take a look at
> MECLIPSE-248,
> > I
> > > > pasted the IRC log url in there.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > I got this error with fresh mvn eclipse:eclipse
> > > >
> > > >
> > > >
> > > > [INFO]
> > > >
> >
>
------------------------------------------------------------------------
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> >
>
------------------------------------------------------------------------
> > > > [INFO] Failed to resolve artifact.
> > > >
> > > > GroupId: org.apache.maven.plugins
> > > > ArtifactId: maven-eclipse-plugin
> > > > Version: test
> > > >
> > > > Reason: Unable to download the artifact from any repository
> > > >
> > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > >
> > > >
> > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > All give the same error
> > > >
> > > >
> > > >
> > > > any suggestions on how to debug this error?
> > > > -Dan
> > > >
> > > >
> > > >
> > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > There's been a lot of discussion in this thread about the
> release.
> > Let
> > > > > me summarize for those trying to keep up:
> > > > >
> > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > Non-Binding: +1 Graham
> > > > >
> > > > > There are some transient issues with the test subsystem used
by
> > > > eclipse
> > > > > that cause failures on Solaris. The issues are with the test
> tools
> > > > > themselves, when the tests execute properly, everything passes
> and
> > > > thus
> > > > > the plugin is doing the correct thing (for the tests that
exist
> > anyway
> > > > > ;-) )
> > > > >
> > > > > At this point, the vote has enough PMC support to release and
> will
> > > > > continue for the remaining ~53hrs. Unless a veto arrives, the
> > release
> > > > > should occur over the weekend.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > To: Maven Developers List
> > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > >
> > > > > It's been about 5 months since an eclipse plugin release and
we
> have
> > > > > lots of fixes and a handful of enhancements:
> > > > >
> > > > > Bug
> > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > javax.servlet:servlet-api:2.3
> > > > > * [MECLIPSE-109] - .component wb-resource source path
incorrect
> for
> > > > ear
> > > > > packaging
> > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> doing
> > mvn
> > > > > eclipse:eclipse for war and ejb projects.
> > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > > > case-sensitive
> > > > > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
> > reuses
> > > > > String method argument causing maven-eclipse.xml
copy-resources
> > > > problems
> > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > > > resolution:=optional directive
> > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement
aren't
> used
> > > > in
> > > > > wtp facet
> > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache
Directory
> > > > Server
> > > > > to be built
> > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api
version
> > > > defined
> > > > > in pom.xml
> > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of
> 5.0 in
> > a
> > > > > Java 5.0 project
> > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > * [MECLIPSE-279] - PDE projects should be considered java
> projects
> > in
> > > > > all cases
> > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > classpath
> > > > > containing dependencies with classifiers
> > > > > Improvement
> > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> servlet
> > > > > version, jsp version, ... possible through pom configuration
> > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> folder
> > > > > creation while executing eclipse:rad
> > > > > New Feature
> > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> projects
> > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > * [MECLIPSE-271] - Ability to skip
> > > > >
> > > > > The site has been updated:
> > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > >
> > > > > Plugin is staged here:
> > > > > http://people.apache.org/~brianf/staging-repository/
> > > > >
> > > > > Vote is open for 72hrs.
> > > > >
> > > > > +1
> > > > >
> > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> >
---------------------------------------------------------------------
> > 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
One more fact on this, I am currently used an internal released version of
eclipse plugin at
r541399, and it works for us. Could there be some changes in between that
may have
trigger this issues. I also tried it with 2.0.5, 2.0.6, and 2.0.7
-D
On 7/6/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> I don't think this is directly a plugin problem. I think there is some
> stray metadata floating in a repo somewhere, possibly left from a bad
> build of the unit tests, which use "test" as the version.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Friday, July 06, 2007 1:59 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> cool, at least someone sees what i see. So this 2.4 release is a nogo.
> -1
> from me.
>
> we should reopen MECLIPSE-248 as well right?
>
> Thanks
>
>
> On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
> >
> > I wrote my problems with it in MECLIPSE-248
> >
> > * the only way to get it work so far is delete the
> > org/apache/maven/plugins/maven-eclipse-plugin folder from the local
> > repo and install the plugin locally
> > * if you install without removing the folder doesn't work
> > * if you remove the folder and let it get downloaded doesn't work
> >
> >
> > On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > > The problem reproducable with maven-scm project even with clean
> local
> > repo.
> > >
> > > I happens on all of my known projects ( ie maven-native at mojo
> > ). Note
> > > all projects
> > > involve reactor mode. Single project seems to be working
> > >
> > > Can some one confirm?
> > >
> > > -D
> > >
> > >
> > >
> > >
> > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > Dan, I saw this on IRC the other day. It was related to some
> > repository
> > > > entries in the project itself, presumably those repos contained
> bad
> > > > metadata but I wasn't able to locate it. Take a look at
> MECLIPSE-248,
> > I
> > > > pasted the IRC log url in there.
> > > >
> > > > -----Original Message-----
> > > > From: Dan Tran [mailto:dantran@gmail.com]
> > > > Sent: Thursday, July 05, 2007 11:01 AM
> > > > To: Maven Developers List
> > > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > > >
> > > > I got this error with fresh mvn eclipse:eclipse
> > > >
> > > >
> > > >
> > > > [INFO]
> > > >
> >
> ------------------------------------------------------------------------
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> >
> ------------------------------------------------------------------------
> > > > [INFO] Failed to resolve artifact.
> > > >
> > > > GroupId: org.apache.maven.plugins
> > > > ArtifactId: maven-eclipse-plugin
> > > > Version: test
> > > >
> > > > Reason: Unable to download the artifact from any repository
> > > >
> > > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > > >
> > > >
> > > > I am using brainf's staged plugin and both built 2.4 tag and
> > > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > > All give the same error
> > > >
> > > >
> > > >
> > > > any suggestions on how to debug this error?
> > > > -Dan
> > > >
> > > >
> > > >
> > > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > > >
> > > > > There's been a lot of discussion in this thread about the
> release.
> > Let
> > > > > me summarize for those trying to keep up:
> > > > >
> > > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > > Non-Binding: +1 Graham
> > > > >
> > > > > There are some transient issues with the test subsystem used by
> > > > eclipse
> > > > > that cause failures on Solaris. The issues are with the test
> tools
> > > > > themselves, when the tests execute properly, everything passes
> and
> > > > thus
> > > > > the plugin is doing the correct thing (for the tests that exist
> > anyway
> > > > > ;-) )
> > > > >
> > > > > At this point, the vote has enough PMC support to release and
> will
> > > > > continue for the remaining ~53hrs. Unless a veto arrives, the
> > release
> > > > > should occur over the weekend.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > > To: Maven Developers List
> > > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > > >
> > > > > It's been about 5 months since an eclipse plugin release and we
> have
> > > > > lots of fixes and a handful of enhancements:
> > > > >
> > > > > Bug
> > > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > > javax.servlet:servlet-api:2.3
> > > > > * [MECLIPSE-109] - .component wb-resource source path incorrect
> for
> > > > ear
> > > > > packaging
> > > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
> doing
> > mvn
> > > > > eclipse:eclipse for war and ejb projects.
> > > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > > > case-sensitive
> > > > > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
> > reuses
> > > > > String method argument causing maven-eclipse.xml copy-resources
> > > > problems
> > > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > > > resolution:=optional directive
> > > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't
> used
> > > > in
> > > > > wtp facet
> > > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> > > > Server
> > > > > to be built
> > > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> > > > defined
> > > > > in pom.xml
> > > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of
> 5.0 in
> > a
> > > > > Java 5.0 project
> > > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > > * [MECLIPSE-279] - PDE projects should be considered java
> projects
> > in
> > > > > all cases
> > > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> > classpath
> > > > > containing dependencies with classifiers
> > > > > Improvement
> > > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
> servlet
> > > > > version, jsp version, ... possible through pom configuration
> > > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
> folder
> > > > > creation while executing eclipse:rad
> > > > > New Feature
> > > > > * [MECLIPSE-119] - Allow custom project name for eclipse
> projects
> > > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > > * [MECLIPSE-271] - Ability to skip
> > > > >
> > > > > The site has been updated:
> > > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > > >
> > > > > Plugin is staged here:
> > > > > http://people.apache.org/~brianf/staging-repository/
> > > > >
> > > > > Vote is open for 72hrs.
> > > > >
> > > > > +1
> > > > >
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > 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
> > > >
> > > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> > ---------------------------------------------------------------------
> > 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I don't think this is directly a plugin problem. I think there is some
stray metadata floating in a repo somewhere, possibly left from a bad
build of the unit tests, which use "test" as the version.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Friday, July 06, 2007 1:59 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
cool, at least someone sees what i see. So this 2.4 release is a nogo.
-1
from me.
we should reopen MECLIPSE-248 as well right?
Thanks
On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> I wrote my problems with it in MECLIPSE-248
>
> * the only way to get it work so far is delete the
> org/apache/maven/plugins/maven-eclipse-plugin folder from the local
> repo and install the plugin locally
> * if you install without removing the folder doesn't work
> * if you remove the folder and let it get downloaded doesn't work
>
>
> On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > The problem reproducable with maven-scm project even with clean
local
> repo.
> >
> > I happens on all of my known projects ( ie maven-native at mojo
> ). Note
> > all projects
> > involve reactor mode. Single project seems to be working
> >
> > Can some one confirm?
> >
> > -D
> >
> >
> >
> >
> > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > Dan, I saw this on IRC the other day. It was related to some
> repository
> > > entries in the project itself, presumably those repos contained
bad
> > > metadata but I wasn't able to locate it. Take a look at
MECLIPSE-248,
> I
> > > pasted the IRC log url in there.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Thursday, July 05, 2007 11:01 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > I got this error with fresh mvn eclipse:eclipse
> > >
> > >
> > >
> > > [INFO]
> > >
>
------------------------------------------------------------------------
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
>
------------------------------------------------------------------------
> > > [INFO] Failed to resolve artifact.
> > >
> > > GroupId: org.apache.maven.plugins
> > > ArtifactId: maven-eclipse-plugin
> > > Version: test
> > >
> > > Reason: Unable to download the artifact from any repository
> > >
> > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > >
> > >
> > > I am using brainf's staged plugin and both built 2.4 tag and
> > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > All give the same error
> > >
> > >
> > >
> > > any suggestions on how to debug this error?
> > > -Dan
> > >
> > >
> > >
> > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > There's been a lot of discussion in this thread about the
release.
> Let
> > > > me summarize for those trying to keep up:
> > > >
> > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > Non-Binding: +1 Graham
> > > >
> > > > There are some transient issues with the test subsystem used by
> > > eclipse
> > > > that cause failures on Solaris. The issues are with the test
tools
> > > > themselves, when the tests execute properly, everything passes
and
> > > thus
> > > > the plugin is doing the correct thing (for the tests that exist
> anyway
> > > > ;-) )
> > > >
> > > > At this point, the vote has enough PMC support to release and
will
> > > > continue for the remaining ~53hrs. Unless a veto arrives, the
> release
> > > > should occur over the weekend.
> > > >
> > > > -----Original Message-----
> > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > To: Maven Developers List
> > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > >
> > > > It's been about 5 months since an eclipse plugin release and we
have
> > > > lots of fixes and a handful of enhancements:
> > > >
> > > > Bug
> > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > javax.servlet:servlet-api:2.3
> > > > * [MECLIPSE-109] - .component wb-resource source path incorrect
for
> > > ear
> > > > packaging
> > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > * [MECLIPSE-220] - Incorrect eclipse facet information when
doing
> mvn
> > > > eclipse:eclipse for war and ejb projects.
> > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > > case-sensitive
> > > > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
> reuses
> > > > String method argument causing maven-eclipse.xml copy-resources
> > > problems
> > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > > resolution:=optional directive
> > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't
used
> > > in
> > > > wtp facet
> > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> > > Server
> > > > to be built
> > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> > > defined
> > > > in pom.xml
> > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of
5.0 in
> a
> > > > Java 5.0 project
> > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > * [MECLIPSE-279] - PDE projects should be considered java
projects
> in
> > > > all cases
> > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> classpath
> > > > containing dependencies with classifiers
> > > > Improvement
> > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
servlet
> > > > version, jsp version, ... possible through pom configuration
> > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6
folder
> > > > creation while executing eclipse:rad
> > > > New Feature
> > > > * [MECLIPSE-119] - Allow custom project name for eclipse
projects
> > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > * [MECLIPSE-271] - Ability to skip
> > > >
> > > > The site has been updated:
> > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > >
> > > > Plugin is staged here:
> > > > http://people.apache.org/~brianf/staging-repository/
> > > >
> > > > Vote is open for 72hrs.
> > > >
> > > > +1
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Max Bowsher <ma...@ukf.net>.
Dan Tran wrote:
> cool, at least someone sees what i see. So this 2.4 release is a nogo. -1
> from me.
>
> we should reopen MECLIPSE-248 as well right?
No, this is not the issue for which I reported MECLIPSE-248, which has
been fixed.
This is a vaguely similar issue which has been conflated with
MECLIPSE-248. A new issue should be created.
Max.
Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
cool, at least someone sees what i see. So this 2.4 release is a nogo. -1
from me.
we should reopen MECLIPSE-248 as well right?
Thanks
On 7/5/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> I wrote my problems with it in MECLIPSE-248
>
> * the only way to get it work so far is delete the
> org/apache/maven/plugins/maven-eclipse-plugin folder from the local
> repo and install the plugin locally
> * if you install without removing the folder doesn't work
> * if you remove the folder and let it get downloaded doesn't work
>
>
> On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> > The problem reproducable with maven-scm project even with clean local
> repo.
> >
> > I happens on all of my known projects ( ie maven-native at mojo
> ). Note
> > all projects
> > involve reactor mode. Single project seems to be working
> >
> > Can some one confirm?
> >
> > -D
> >
> >
> >
> >
> > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > Dan, I saw this on IRC the other day. It was related to some
> repository
> > > entries in the project itself, presumably those repos contained bad
> > > metadata but I wasn't able to locate it. Take a look at MECLIPSE-248,
> I
> > > pasted the IRC log url in there.
> > >
> > > -----Original Message-----
> > > From: Dan Tran [mailto:dantran@gmail.com]
> > > Sent: Thursday, July 05, 2007 11:01 AM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> > >
> > > I got this error with fresh mvn eclipse:eclipse
> > >
> > >
> > >
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Failed to resolve artifact.
> > >
> > > GroupId: org.apache.maven.plugins
> > > ArtifactId: maven-eclipse-plugin
> > > Version: test
> > >
> > > Reason: Unable to download the artifact from any repository
> > >
> > > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> > >
> > >
> > > I am using brainf's staged plugin and both built 2.4 tag and
> > > 2.5-SNAPSHOTand wiped out my local repo as well
> > > All give the same error
> > >
> > >
> > >
> > > any suggestions on how to debug this error?
> > > -Dan
> > >
> > >
> > >
> > > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > There's been a lot of discussion in this thread about the release.
> Let
> > > > me summarize for those trying to keep up:
> > > >
> > > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > > Non-Binding: +1 Graham
> > > >
> > > > There are some transient issues with the test subsystem used by
> > > eclipse
> > > > that cause failures on Solaris. The issues are with the test tools
> > > > themselves, when the tests execute properly, everything passes and
> > > thus
> > > > the plugin is doing the correct thing (for the tests that exist
> anyway
> > > > ;-) )
> > > >
> > > > At this point, the vote has enough PMC support to release and will
> > > > continue for the remaining ~53hrs. Unless a veto arrives, the
> release
> > > > should occur over the weekend.
> > > >
> > > > -----Original Message-----
> > > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > > To: Maven Developers List
> > > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > > >
> > > > It's been about 5 months since an eclipse plugin release and we have
> > > > lots of fixes and a handful of enhancements:
> > > >
> > > > Bug
> > > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > > javax.servlet:servlet-api:2.3
> > > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> > > ear
> > > > packaging
> > > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > > * [MECLIPSE-198] - EJB version is not resloved
> > > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > > * [MECLIPSE-220] - Incorrect eclipse facet information when doing
> mvn
> > > > eclipse:eclipse for war and ejb projects.
> > > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > > case-sensitive
> > > > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
> reuses
> > > > String method argument causing maven-eclipse.xml copy-resources
> > > problems
> > > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > > resolution:=optional directive
> > > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
> > > in
> > > > wtp facet
> > > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> > > Server
> > > > to be built
> > > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> > > defined
> > > > in pom.xml
> > > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in
> a
> > > > Java 5.0 project
> > > > * [MECLIPSE-278] - duplicated classpathentries
> > > > * [MECLIPSE-279] - PDE projects should be considered java projects
> in
> > > > all cases
> > > > * [MECLIPSE-287] - Regression - fails to correctly construct
> classpath
> > > > containing dependencies with classifiers
> > > > Improvement
> > > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> > > > version, jsp version, ... possible through pom configuration
> > > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> > > > creation while executing eclipse:rad
> > > > New Feature
> > > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> > > > * [MECLIPSE-189] - addVersionToProjectName property
> > > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > > * [MECLIPSE-271] - Ability to skip
> > > >
> > > > The site has been updated:
> > > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > > >
> > > > Plugin is staged here:
> > > > http://people.apache.org/~brianf/staging-repository/
> > > >
> > > > Vote is open for 72hrs.
> > > >
> > > > +1
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Carlos Sanchez <ca...@apache.org>.
I wrote my problems with it in MECLIPSE-248
* the only way to get it work so far is delete the
org/apache/maven/plugins/maven-eclipse-plugin folder from the local
repo and install the plugin locally
* if you install without removing the folder doesn't work
* if you remove the folder and let it get downloaded doesn't work
On 7/5/07, Dan Tran <da...@gmail.com> wrote:
> The problem reproducable with maven-scm project even with clean local repo.
>
> I happens on all of my known projects ( ie maven-native at mojo ). Note
> all projects
> involve reactor mode. Single project seems to be working
>
> Can some one confirm?
>
> -D
>
>
>
>
> On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > Dan, I saw this on IRC the other day. It was related to some repository
> > entries in the project itself, presumably those repos contained bad
> > metadata but I wasn't able to locate it. Take a look at MECLIPSE-248, I
> > pasted the IRC log url in there.
> >
> > -----Original Message-----
> > From: Dan Tran [mailto:dantran@gmail.com]
> > Sent: Thursday, July 05, 2007 11:01 AM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
> >
> > I got this error with fresh mvn eclipse:eclipse
> >
> >
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Failed to resolve artifact.
> >
> > GroupId: org.apache.maven.plugins
> > ArtifactId: maven-eclipse-plugin
> > Version: test
> >
> > Reason: Unable to download the artifact from any repository
> >
> > org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> >
> >
> > I am using brainf's staged plugin and both built 2.4 tag and
> > 2.5-SNAPSHOTand wiped out my local repo as well
> > All give the same error
> >
> >
> >
> > any suggestions on how to debug this error?
> > -Dan
> >
> >
> >
> > On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > There's been a lot of discussion in this thread about the release. Let
> > > me summarize for those trying to keep up:
> > >
> > > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > > Non-Binding: +1 Graham
> > >
> > > There are some transient issues with the test subsystem used by
> > eclipse
> > > that cause failures on Solaris. The issues are with the test tools
> > > themselves, when the tests execute properly, everything passes and
> > thus
> > > the plugin is doing the correct thing (for the tests that exist anyway
> > > ;-) )
> > >
> > > At this point, the vote has enough PMC support to release and will
> > > continue for the remaining ~53hrs. Unless a veto arrives, the release
> > > should occur over the weekend.
> > >
> > > -----Original Message-----
> > > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > > Sent: Wednesday, July 04, 2007 3:39 PM
> > > To: Maven Developers List
> > > Subject: [VOTE] maven-eclipse-plugin 2.4
> > >
> > > It's been about 5 months since an eclipse plugin release and we have
> > > lots of fixes and a handful of enhancements:
> > >
> > > Bug
> > > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > > javax.servlet:servlet-api:2.3
> > > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> > ear
> > > packaging
> > > * [MECLIPSE-151] - Incorrect name for test sources jars
> > > * [MECLIPSE-198] - EJB version is not resloved
> > > * [MECLIPSE-215] - WTP 1.5 Documentation
> > > * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> > > eclipse:eclipse for war and ejb projects.
> > > * [MECLIPSE-225] - Invalid .classpath Entries.
> > > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > > case-sensitive
> > > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> > > String method argument causing maven-eclipse.xml copy-resources
> > problems
> > > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > > resolution:=optional directive
> > > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
> > in
> > > wtp facet
> > > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> > Server
> > > to be built
> > > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> > defined
> > > in pom.xml
> > > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> > > Java 5.0 project
> > > * [MECLIPSE-278] - duplicated classpathentries
> > > * [MECLIPSE-279] - PDE projects should be considered java projects in
> > > all cases
> > > * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> > > containing dependencies with classifiers
> > > Improvement
> > > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> > > version, jsp version, ... possible through pom configuration
> > > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> > > creation while executing eclipse:rad
> > > New Feature
> > > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> > > * [MECLIPSE-189] - addVersionToProjectName property
> > > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > > * [MECLIPSE-271] - Ability to skip
> > >
> > > The site has been updated:
> > > http://maven.apache.org/plugins/maven-eclipse-plugin
> > >
> > > Plugin is staged here:
> > > http://people.apache.org/~brianf/staging-repository/
> > >
> > > Vote is open for 72hrs.
> > >
> > > +1
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
The problem reproducable with maven-scm project even with clean local repo.
I happens on all of my known projects ( ie maven-native at mojo ). Note
all projects
involve reactor mode. Single project seems to be working
Can some one confirm?
-D
On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> Dan, I saw this on IRC the other day. It was related to some repository
> entries in the project itself, presumably those repos contained bad
> metadata but I wasn't able to locate it. Take a look at MECLIPSE-248, I
> pasted the IRC log url in there.
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Thursday, July 05, 2007 11:01 AM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
>
> I got this error with fresh mvn eclipse:eclipse
>
>
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> GroupId: org.apache.maven.plugins
> ArtifactId: maven-eclipse-plugin
> Version: test
>
> Reason: Unable to download the artifact from any repository
>
> org.apache.maven.plugins:maven-eclipse-plugin:pom:test
>
>
> I am using brainf's staged plugin and both built 2.4 tag and
> 2.5-SNAPSHOTand wiped out my local repo as well
> All give the same error
>
>
>
> any suggestions on how to debug this error?
> -Dan
>
>
>
> On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > There's been a lot of discussion in this thread about the release. Let
> > me summarize for those trying to keep up:
> >
> > Binding: +4 Brian, Arnaud, Vincent, Kenney
> > Non-Binding: +1 Graham
> >
> > There are some transient issues with the test subsystem used by
> eclipse
> > that cause failures on Solaris. The issues are with the test tools
> > themselves, when the tests execute properly, everything passes and
> thus
> > the plugin is doing the correct thing (for the tests that exist anyway
> > ;-) )
> >
> > At this point, the vote has enough PMC support to release and will
> > continue for the remaining ~53hrs. Unless a veto arrives, the release
> > should occur over the weekend.
> >
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Wednesday, July 04, 2007 3:39 PM
> > To: Maven Developers List
> > Subject: [VOTE] maven-eclipse-plugin 2.4
> >
> > It's been about 5 months since an eclipse plugin release and we have
> > lots of fixes and a handful of enhancements:
> >
> > Bug
> > * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> > javax.servlet:servlet-api:2.3
> > * [MECLIPSE-109] - .component wb-resource source path incorrect for
> ear
> > packaging
> > * [MECLIPSE-151] - Incorrect name for test sources jars
> > * [MECLIPSE-198] - EJB version is not resloved
> > * [MECLIPSE-215] - WTP 1.5 Documentation
> > * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> > eclipse:eclipse for war and ejb projects.
> > * [MECLIPSE-225] - Invalid .classpath Entries.
> > * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> > case-sensitive
> > * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> > String method argument causing maven-eclipse.xml copy-resources
> problems
> > * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> > resolution:=optional directive
> > * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> > * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
> in
> > wtp facet
> > * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> Server
> > to be built
> > * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> > * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> defined
> > in pom.xml
> > * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> > Java 5.0 project
> > * [MECLIPSE-278] - duplicated classpathentries
> > * [MECLIPSE-279] - PDE projects should be considered java projects in
> > all cases
> > * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> > containing dependencies with classifiers
> > Improvement
> > * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> > * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> > * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> > version, jsp version, ... possible through pom configuration
> > * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> > creation while executing eclipse:rad
> > New Feature
> > * [MECLIPSE-119] - Allow custom project name for eclipse projects
> > * [MECLIPSE-189] - addVersionToProjectName property
> > * [MECLIPSE-251] - Allows prefixing of eclipse project name
> > * [MECLIPSE-271] - Ability to skip
> >
> > The site has been updated:
> > http://maven.apache.org/plugins/maven-eclipse-plugin
> >
> > Plugin is staged here:
> > http://people.apache.org/~brianf/staging-repository/
> >
> > Vote is open for 72hrs.
> >
> > +1
> >
> >
> > ---------------------------------------------------------------------
> > 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Dan, I saw this on IRC the other day. It was related to some repository
entries in the project itself, presumably those repos contained bad
metadata but I wasn't able to locate it. Take a look at MECLIPSE-248, I
pasted the IRC log url in there.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Thursday, July 05, 2007 11:01 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
I got this error with fresh mvn eclipse:eclipse
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-eclipse-plugin
Version: test
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-eclipse-plugin:pom:test
I am using brainf's staged plugin and both built 2.4 tag and
2.5-SNAPSHOTand wiped out my local repo as well
All give the same error
any suggestions on how to debug this error?
-Dan
On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> There's been a lot of discussion in this thread about the release. Let
> me summarize for those trying to keep up:
>
> Binding: +4 Brian, Arnaud, Vincent, Kenney
> Non-Binding: +1 Graham
>
> There are some transient issues with the test subsystem used by
eclipse
> that cause failures on Solaris. The issues are with the test tools
> themselves, when the tests execute properly, everything passes and
thus
> the plugin is doing the correct thing (for the tests that exist anyway
> ;-) )
>
> At this point, the vote has enough PMC support to release and will
> continue for the remaining ~53hrs. Unless a veto arrives, the release
> should occur over the weekend.
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, July 04, 2007 3:39 PM
> To: Maven Developers List
> Subject: [VOTE] maven-eclipse-plugin 2.4
>
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements:
>
> Bug
> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> javax.servlet:servlet-api:2.3
> * [MECLIPSE-109] - .component wb-resource source path incorrect for
ear
> packaging
> * [MECLIPSE-151] - Incorrect name for test sources jars
> * [MECLIPSE-198] - EJB version is not resloved
> * [MECLIPSE-215] - WTP 1.5 Documentation
> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> eclipse:eclipse for war and ejb projects.
> * [MECLIPSE-225] - Invalid .classpath Entries.
> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> case-sensitive
> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> String method argument causing maven-eclipse.xml copy-resources
problems
> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> resolution:=optional directive
> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used
in
> wtp facet
> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
Server
> to be built
> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
defined
> in pom.xml
> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> Java 5.0 project
> * [MECLIPSE-278] - duplicated classpathentries
> * [MECLIPSE-279] - PDE projects should be considered java projects in
> all cases
> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> containing dependencies with classifiers
> Improvement
> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> version, jsp version, ... possible through pom configuration
> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> creation while executing eclipse:rad
> New Feature
> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> * [MECLIPSE-189] - addVersionToProjectName property
> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> * [MECLIPSE-271] - Ability to skip
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/staging-repository/
>
> Vote is open for 72hrs.
>
> +1
>
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by Dan Tran <da...@gmail.com>.
I got this error with fresh mvn eclipse:eclipse
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-eclipse-plugin
Version: test
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-eclipse-plugin:pom:test
I am using brainf's staged plugin and both built 2.4 tag and
2.5-SNAPSHOTand wiped out my local repo as well
All give the same error
any suggestions on how to debug this error?
-Dan
On 7/5/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> There's been a lot of discussion in this thread about the release. Let
> me summarize for those trying to keep up:
>
> Binding: +4 Brian, Arnaud, Vincent, Kenney
> Non-Binding: +1 Graham
>
> There are some transient issues with the test subsystem used by eclipse
> that cause failures on Solaris. The issues are with the test tools
> themselves, when the tests execute properly, everything passes and thus
> the plugin is doing the correct thing (for the tests that exist anyway
> ;-) )
>
> At this point, the vote has enough PMC support to release and will
> continue for the remaining ~53hrs. Unless a veto arrives, the release
> should occur over the weekend.
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, July 04, 2007 3:39 PM
> To: Maven Developers List
> Subject: [VOTE] maven-eclipse-plugin 2.4
>
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements:
>
> Bug
> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> javax.servlet:servlet-api:2.3
> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear
> packaging
> * [MECLIPSE-151] - Incorrect name for test sources jars
> * [MECLIPSE-198] - EJB version is not resloved
> * [MECLIPSE-215] - WTP 1.5 Documentation
> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> eclipse:eclipse for war and ejb projects.
> * [MECLIPSE-225] - Invalid .classpath Entries.
> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> case-sensitive
> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> String method argument causing maven-eclipse.xml copy-resources problems
> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> resolution:=optional directive
> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
> wtp facet
> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
> to be built
> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
> in pom.xml
> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> Java 5.0 project
> * [MECLIPSE-278] - duplicated classpathentries
> * [MECLIPSE-279] - PDE projects should be considered java projects in
> all cases
> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> containing dependencies with classifiers
> Improvement
> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> version, jsp version, ... possible through pom configuration
> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> creation while executing eclipse:rad
> New Feature
> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> * [MECLIPSE-189] - addVersionToProjectName property
> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> * [MECLIPSE-271] - Ability to skip
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/staging-repository/
>
> Vote is open for 72hrs.
>
> +1
>
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
There's been a lot of discussion in this thread about the release. Let
me summarize for those trying to keep up:
Binding: +4 Brian, Arnaud, Vincent, Kenney
Non-Binding: +1 Graham
There are some transient issues with the test subsystem used by eclipse
that cause failures on Solaris. The issues are with the test tools
themselves, when the tests execute properly, everything passes and thus
the plugin is doing the correct thing (for the tests that exist anyway
;-) )
At this point, the vote has enough PMC support to release and will
continue for the remaining ~53hrs. Unless a veto arrives, the release
should occur over the weekend.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, July 04, 2007 3:39 PM
To: Maven Developers List
Subject: [VOTE] maven-eclipse-plugin 2.4
It's been about 5 months since an eclipse plugin release and we have
lots of fixes and a handful of enhancements:
Bug
* [MECLIPSE-108] - .wtpmodules with version 2.4 for
javax.servlet:servlet-api:2.3
* [MECLIPSE-109] - .component wb-resource source path incorrect for ear
packaging
* [MECLIPSE-151] - Incorrect name for test sources jars
* [MECLIPSE-198] - EJB version is not resloved
* [MECLIPSE-215] - WTP 1.5 Documentation
* [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
eclipse:eclipse for war and ejb projects.
* [MECLIPSE-225] - Invalid .classpath Entries.
* [MECLIPSE-233] - Manifest attributes incorrectly treated as
case-sensitive
* [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
String method argument causing maven-eclipse.xml copy-resources problems
* [MECLIPSE-236] - eclipse:make-artifacts should preserve the
resolution:=optional directive
* [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
* [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
wtp facet
* [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
to be built
* [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
* [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
in pom.xml
* [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
Java 5.0 project
* [MECLIPSE-278] - duplicated classpathentries
* [MECLIPSE-279] - PDE projects should be considered java projects in
all cases
* [MECLIPSE-287] - Regression - fails to correctly construct classpath
containing dependencies with classifiers
Improvement
* [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
* [MECLIPSE-267] - Resolve version ranges in make-artifacts
* [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
version, jsp version, ... possible through pom configuration
* [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
creation while executing eclipse:rad
New Feature
* [MECLIPSE-119] - Allow custom project name for eclipse projects
* [MECLIPSE-189] - addVersionToProjectName property
* [MECLIPSE-251] - Allows prefixing of eclipse project name
* [MECLIPSE-271] - Ability to skip
The site has been updated:
http://maven.apache.org/plugins/maven-eclipse-plugin
Plugin is staged here:
http://people.apache.org/~brianf/staging-repository/
Vote is open for 72hrs.
+1
---------------------------------------------------------------------
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] maven-eclipse-plugin 2.4
Posted by Barrie Treloar <ba...@gmail.com>.
> That would work fine to allow trialling the plugin against various
> projects on the command line.
>
> The other part of testing would be to check out the svn tag and verify
> that it builds.
>
> > What happens when the real thing is released? Will my local repo be
> > polluted with the staging details and I need to clean it up?
>
> If you don't build it yourself, and the staged version is released
> unchanged, then that's mostly not a problem - though there'd be some
> metadata xml files left over in the local repo.
>
> If you do build it yourself, then you'd *hope* you'd have an exact
> workalike to the release, but it won't be bytewise identical, so you
> probably ought to call that pollution, and clean it up.
>
> And of course, there's the possibility that this staging iteration
> doesn't succeed, in which case, it's *definitely* pollution in the local
> repo that needs to be cleaned up.
Thanks, I will post a separate question to find out what others are
doing and if there is a preferred approach.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Max Bowsher <ma...@ukf.net>.
Barrie Treloar wrote:
> Apologies for the noob question, but how do I test the stage release?
> (I had a quick look at
> http://docs.codehaus.org/display/MAVEN/Development+Process and
> http://docs.codehaus.org/display/MAVEN/Development+Procedures but
> couldn't find it).
>
> Is it just a matter of defining
> http://people.apache.org/~brianf/staging-repository/ as a repo in
> settings.xml as:
>
> <profile>
> <id>staging</id>
> <repositories>
> <pluginRepositories>
> <pluginRepository>
> <id>staging</id>
> <name>Maven Plugin Staging Repository</name>
> <url>http://people.apache.org/~brianf/staging-repository/</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> </pluginRepository>
> </pluginRepositories>
> </profile>
That would work fine to allow trialling the plugin against various
projects on the command line.
The other part of testing would be to check out the svn tag and verify
that it builds.
> What happens when the real thing is released? Will my local repo be
> polluted with the staging details and I need to clean it up?
If you don't build it yourself, and the staged version is released
unchanged, then that's mostly not a problem - though there'd be some
metadata xml files left over in the local repo.
If you do build it yourself, then you'd *hope* you'd have an exact
workalike to the release, but it won't be bytewise identical, so you
probably ought to call that pollution, and clean it up.
And of course, there's the possibility that this staging iteration
doesn't succeed, in which case, it's *definitely* pollution in the local
repo that needs to be cleaned up.
Max.
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Barrie Treloar <ba...@gmail.com>.
Apologies for the noob question, but how do I test the stage release?
(I had a quick look at
http://docs.codehaus.org/display/MAVEN/Development+Process and
http://docs.codehaus.org/display/MAVEN/Development+Procedures but
couldn't find it).
Is it just a matter of defining
http://people.apache.org/~brianf/staging-repository/ as a repo in
settings.xml as:
<profile>
<id>staging</id>
<repositories>
<pluginRepositories>
<pluginRepository>
<id>staging</id>
<name>Maven Plugin Staging Repository</name>
<url>http://people.apache.org/~brianf/staging-repository/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
What happens when the real thing is released? Will my local repo be
polluted with the staging details and I need to clean it up?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Max Bowsher <ma...@ukf.net>.
Brian E. Fox wrote:
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements:
>
...
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/staging-repository/
So the Subversion tag is:
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.4/
Max.
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Kenney Westerhof <ke...@apache.org>.
Final update: I checked out the tag cleanly, ran another build
and it passed fine.
The build took 9 mins 37 seconds. Ridiculous, but:
+1
Kenney Westerhof wrote:
> Update:
>
> It seems i was impatient, it took almost 3 minutes to run that single test.
> After that it continued (on 2.0.7), but I got a failure:
>
> -------------------------------------------------------------------------------
>
> Test set: org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest
> -------------------------------------------------------------------------------
>
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 39.878
> sec <<< FAILURE!
> testModule1Project(org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest)
> Time elapsed: 11.979 sec <<< ERROR!
> org.apache.maven.plugin.eclipse.ExecutionFailedException: Failed to
> execute build.
> POM:
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/projects/master-test/pom.xml
>
> Goals: org.apache.maven.plugins:maven-eclipse-plugin:test:clean,
> org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse
> Exit Code: 1
> Error: null
> Build Log:
> file:/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports/build-output/org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest_testModule1Project.build.log
>
> (Resulting exit code: 1)
> at
> org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.executeMaven(AbstractEclipsePluginTestCase.java:309)
>
>
> Last part of the file:/ indicated above:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to
> find the mojo
> 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the
> plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> Component descriptor cannot be found in the component repository:
> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
>
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
> in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to
> find the mojo
> 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the
> plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginManagerException: Unable to
> find the mojo
> 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the
> plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>
> ... 16 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
>
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
>
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
>
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562)
>
> ... 18 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 9 seconds
>
>
> btw, tests take about 7 minutes whereas bootstrapping maven itself takes
> only 3 minutes.
>
> my -1 stands, unless I'm the only one where this fails.
>
> -- Kenney
>
> Kenney Westerhof wrote:
>> I assume this is a vote to _release_ maven-eclipse-plugin 2.4.
>>
>> -1 until the tests are fixed:
>>
>>
>> [INFO] [surefire:test]
>> [INFO] Surefire report directory:
>> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports
>>
>>
>> -------------------------------------------------------
>> T E S T S
>> -------------------------------------------------------
>> Running org.apache.maven.plugin.eclipse.AddMavenRepoMojoTest
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.899 sec
>> Running
>> org.apache.maven.plugin.eclipse.writers.EclipseOSGiManifestWriterTest
>> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
>> Running org.apache.maven.plugin.eclipse.RadPluginTest
>> *** Running test builds; output will be directed to:
>> target/surefire-reports/build-output
>>
>> [INFO] Installing target/maven-eclipse-plugin-test.jar to
>> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.jar
>>
>> [INFO] Installing ../pom.xml to
>> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-plugins/9-SNAPSHOT/maven-plugins-9-SNAPSHOT.pom
>>
>> [INFO] Installing ../../pom/maven/pom.xml to
>> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/maven-parent/6-SNAPSHOT/maven-parent-6-SNAPSHOT.pom
>>
>> [INFO] Installing ../../pom/maven/../asf/pom.xml to
>> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/apache/5-SNAPSHOT/apache-5-SNAPSHOT.pom
>>
>> *** Installed test-version of the Eclipse plugin to:
>> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo
>>
>>
>> and it indefinitely hangs at this point, no cpu load.
>>
>>
>> Tested with maven 2.1 and 2.0.7.
>> Otherwise the plugin works great.
>>
>> -- Kenney
>>
>> Brian E. Fox wrote:
>>> It's been about 5 months since an eclipse plugin release and we have
>>> lots of fixes and a handful of enhancements:
>>>
>>> Bug
>>> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>>> javax.servlet:servlet-api:2.3
>>> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear
>>> packaging
>>> * [MECLIPSE-151] - Incorrect name for test sources jars
>>> * [MECLIPSE-198] - EJB version is not resloved
>>> * [MECLIPSE-215] - WTP 1.5 Documentation
>>> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
>>> eclipse:eclipse for war and ejb projects.
>>> * [MECLIPSE-225] - Invalid .classpath Entries.
>>> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>>> case-sensitive
>>> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
>>> String method argument causing maven-eclipse.xml copy-resources problems
>>> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>>> resolution:=optional directive
>>> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>>> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
>>> wtp facet
>>> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
>>> to be built
>>> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>>> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
>>> in pom.xml
>>> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
>>> Java 5.0 project
>>> * [MECLIPSE-278] - duplicated classpathentries
>>> * [MECLIPSE-279] - PDE projects should be considered java projects in
>>> all cases
>>> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
>>> containing dependencies with classifiers
>>> Improvement
>>> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>>> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>>> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>>> version, jsp version, ... possible through pom configuration
>>> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>>> creation while executing eclipse:rad
>>> New Feature
>>> * [MECLIPSE-119] - Allow custom project name for eclipse projects
>>> * [MECLIPSE-189] - addVersionToProjectName property
>>> * [MECLIPSE-251] - Allows prefixing of eclipse project name
>>> * [MECLIPSE-271] - Ability to skip
>>>
>>> The site has been updated:
>>> http://maven.apache.org/plugins/maven-eclipse-plugin
>>>
>>> Plugin is staged here:
>>> http://people.apache.org/~brianf/staging-repository/
>>>
>>> Vote is open for 72hrs.
>>>
>>> +1
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The tests issue seems to be a transient test subsystem problem, not an
issue with the actual plugin. If tests of the plugin do work as expected
when the subsystem holds up, should this really hold a release? Take a
look at MECLIPSE-248 to see if the suggestions in there clear up the
tests on solaris for you.
-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
Sent: Wednesday, July 04, 2007 7:22 PM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4
Same thing here:
Tests work on windows, failed on solaris so -1 too
Cheers,
Vincent
2007/7/4, Kenney Westerhof <ke...@apache.org>:
> Update:
>
> It seems i was impatient, it took almost 3 minutes to run that single
test.
> After that it continued (on 2.0.7), but I got a failure:
>
>
------------------------------------------------------------------------
-------
> Test set:
org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest
>
------------------------------------------------------------------------
-------
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 39.878
sec <<< FAILURE!
>
testModule1Project(org.apache.maven.plugin.eclipse.EclipsePluginMasterPr
ojectTest) Time elapsed: 11.979 sec <<< ERROR!
> org.apache.maven.plugin.eclipse.ExecutionFailedException: Failed to
execute build.
> POM:
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/test-classes/projects/master-test/pom.xml
> Goals: org.apache.maven.plugins:maven-eclipse-plugin:test:clean,
org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse
> Exit Code: 1
> Error: null
> Build Log:
file:/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclip
se-plugin/target/surefire-reports/build-output/org.apache.maven.plugin.e
clipse.EclipsePluginMasterProjectTest_testModule1Project.build.log
> (Resulting exit code: 1)
> at
org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.executeMav
en(AbstractEclipsePluginTestCase.java:309)
>
> Last part of the file:/ indicated above:
>
> [ERROR] BUILD ERROR
> [INFO]
------------------------------------------------------------------------
> [INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to
find the mojo
'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the
plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugi
n:test:eclipse.
> [INFO]
------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to
find the mojo
'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the
plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:543)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.java:493)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:463)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:143)
> at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginManagerException: Unable to
find the mojo
'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the
plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
uginManager.java:571)
> at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:421)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:539)
> ... 16 more
> Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion: Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugi
n:test:eclipse.
> at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:323)
> at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:312)
> at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:440)
> at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
uginManager.java:562)
> ... 18 more
> [INFO]
------------------------------------------------------------------------
> [INFO] Total time: 9 seconds
>
>
> btw, tests take about 7 minutes whereas bootstrapping maven itself
takes only 3 minutes.
>
> my -1 stands, unless I'm the only one where this fails.
>
> -- Kenney
>
> Kenney Westerhof wrote:
> > I assume this is a vote to _release_ maven-eclipse-plugin 2.4.
> >
> > -1 until the tests are fixed:
> >
> >
> > [INFO] [surefire:test]
> > [INFO] Surefire report directory:
> >
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/surefire-reports
> >
> >
> > -------------------------------------------------------
> > T E S T S
> > -------------------------------------------------------
> > Running org.apache.maven.plugin.eclipse.AddMavenRepoMojoTest
> > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.899 sec
> > Running
> >
org.apache.maven.plugin.eclipse.writers.EclipseOSGiManifestWriterTest
> > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.011 sec
> > Running org.apache.maven.plugin.eclipse.RadPluginTest
> > *** Running test builds; output will be directed to:
> > target/surefire-reports/build-output
> >
> > [INFO] Installing target/maven-eclipse-plugin-test.jar to
> >
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-eclipse-p
lugin/test/maven-eclipse-plugin-test.jar
> >
> > [INFO] Installing ../pom.xml to
> >
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-plugins/9
-SNAPSHOT/maven-plugins-9-SNAPSHOT.pom
> >
> > [INFO] Installing ../../pom/maven/pom.xml to
> >
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/test-classes/m2repo/org/apache/maven/maven-parent/6-SNAPSHOT
/maven-parent-6-SNAPSHOT.pom
> >
> > [INFO] Installing ../../pom/maven/../asf/pom.xml to
> >
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/test-classes/m2repo/org/apache/apache/5-SNAPSHOT/apache-5-SN
APSHOT.pom
> >
> > *** Installed test-version of the Eclipse plugin to:
> >
/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl
ugin/target/test-classes/m2repo
> >
> >
> > and it indefinitely hangs at this point, no cpu load.
> >
> >
> > Tested with maven 2.1 and 2.0.7.
> > Otherwise the plugin works great.
> >
> > -- Kenney
> >
> > Brian E. Fox wrote:
> >> It's been about 5 months since an eclipse plugin release and we
have
> >> lots of fixes and a handful of enhancements:
> >>
> >> Bug
> >> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> >> javax.servlet:servlet-api:2.3
> >> * [MECLIPSE-109] - .component wb-resource source path incorrect for
ear
> >> packaging
> >> * [MECLIPSE-151] - Incorrect name for test sources jars
> >> * [MECLIPSE-198] - EJB version is not resloved
> >> * [MECLIPSE-215] - WTP 1.5 Documentation
> >> * [MECLIPSE-220] - Incorrect eclipse facet information when doing
mvn
> >> eclipse:eclipse for war and ejb projects.
> >> * [MECLIPSE-225] - Invalid .classpath Entries.
> >> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> >> case-sensitive
> >> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
reuses
> >> String method argument causing maven-eclipse.xml copy-resources
problems
> >> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> >> resolution:=optional directive
> >> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> >> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't
used in
> >> wtp facet
> >> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
Server
> >> to be built
> >> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> >> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
defined
> >> in pom.xml
> >> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0
in a
> >> Java 5.0 project
> >> * [MECLIPSE-278] - duplicated classpathentries
> >> * [MECLIPSE-279] - PDE projects should be considered java projects
in
> >> all cases
> >> * [MECLIPSE-287] - Regression - fails to correctly construct
classpath
> >> containing dependencies with classifiers
> >> Improvement
> >> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> >> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> >> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> >> version, jsp version, ... possible through pom configuration
> >> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> >> creation while executing eclipse:rad
> >> New Feature
> >> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> >> * [MECLIPSE-189] - addVersionToProjectName property
> >> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> >> * [MECLIPSE-271] - Ability to skip
> >>
> >> The site has been updated:
> >> http://maven.apache.org/plugins/maven-eclipse-plugin
> >>
> >> Plugin is staged here:
> >> http://people.apache.org/~brianf/staging-repository/
> >>
> >> Vote is open for 72hrs.
> >>
> >> +1
> >>
> >>
> >>
---------------------------------------------------------------------
> >> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Vincent Siveton <vi...@gmail.com>.
This issue is related to the tools and not the plugin.
So I change my vote to +1
Cheers,
Vincent
2007/7/5, Vincent Siveton <vi...@gmail.com>:
> Hi Brian,
>
> My mistake:
> compilation success with maven-test-tools:1.0-alpha-2-SNAPSHOT
> But tests failed again :(
> Weird: continuum seems happy. Someone could try too?
>
> Vincent
>
> 2007/7/4, Brian E. Fox <br...@reply.infinity.nu>:
> > Really? I'm able to build it no problems. What's the error?
> >
> > -----Original Message-----
> > From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> > Sent: Wednesday, July 04, 2007 10:59 PM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4
> >
> > Compilation failure with 1.0-alpha-2-SNAPSHOT so cant try.
> >
> > Vincent
> >
> > 2007/7/4, Brian E. Fox <br...@reply.infinity.nu>:
> > > Looks like an issue in the test tools. Can you try bumping the
> > > dependency back to 1.0-alpha-2-SNAPSHOT? It didn't seem to be required
> > > for me, but it's worth a shot.
> > >
> > > -----Original Message-----
> > > From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> > > Sent: Wednesday, July 04, 2007 10:04 PM
> > > To: Maven Developers List
> > > Subject: Re: [VOTE] maven-eclipse-plugin 2.4
> > >
> > > Hi Max,
> > >
> > > I confirm that it was on this tag. Here are the failing logs (Using
> > > maven 2.0.7):
> > >
> > http://people.apache.org/~vsiveton/maven-eclipse-plugin-2.4/target/suref
> > > ire-reports/
> > >
> > > It seems that target/maven-eclipse-plugin-test.jar was not build on
> > > solaris.
> > >
> > > Someone could confirm?
> > >
> > > Cheers,
> > >
> > > Vincent
> > >
> > > 2007/7/4, Max Bowsher <ma...@ukf.net>:
> > > > Vincent Siveton wrote:
> > > > > Same thing here:
> > > > > Tests work on windows, failed on solaris so -1 too
> > > >
> > > > Could you confirm what it was that you were building? Was it the
> > tag,
> > > >
> > >
> > http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-
> > > 2.4/
> > > > ?
> > > >
> > > > If not, could you re-test, using that.
> > > >
> > > > If you're still getting errors, could you put the build logs
> > somewhere
> > > > downloadable?
> > > >
> > > > Thanks,
> > > > Max.
> > > >
> > > >
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Brian,
My mistake:
compilation success with maven-test-tools:1.0-alpha-2-SNAPSHOT
But tests failed again :(
Weird: continuum seems happy. Someone could try too?
Vincent
2007/7/4, Brian E. Fox <br...@reply.infinity.nu>:
> Really? I'm able to build it no problems. What's the error?
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Wednesday, July 04, 2007 10:59 PM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> Compilation failure with 1.0-alpha-2-SNAPSHOT so cant try.
>
> Vincent
>
> 2007/7/4, Brian E. Fox <br...@reply.infinity.nu>:
> > Looks like an issue in the test tools. Can you try bumping the
> > dependency back to 1.0-alpha-2-SNAPSHOT? It didn't seem to be required
> > for me, but it's worth a shot.
> >
> > -----Original Message-----
> > From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> > Sent: Wednesday, July 04, 2007 10:04 PM
> > To: Maven Developers List
> > Subject: Re: [VOTE] maven-eclipse-plugin 2.4
> >
> > Hi Max,
> >
> > I confirm that it was on this tag. Here are the failing logs (Using
> > maven 2.0.7):
> >
> http://people.apache.org/~vsiveton/maven-eclipse-plugin-2.4/target/suref
> > ire-reports/
> >
> > It seems that target/maven-eclipse-plugin-test.jar was not build on
> > solaris.
> >
> > Someone could confirm?
> >
> > Cheers,
> >
> > Vincent
> >
> > 2007/7/4, Max Bowsher <ma...@ukf.net>:
> > > Vincent Siveton wrote:
> > > > Same thing here:
> > > > Tests work on windows, failed on solaris so -1 too
> > >
> > > Could you confirm what it was that you were building? Was it the
> tag,
> > >
> >
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-
> > 2.4/
> > > ?
> > >
> > > If not, could you re-test, using that.
> > >
> > > If you're still getting errors, could you put the build logs
> somewhere
> > > downloadable?
> > >
> > > Thanks,
> > > Max.
> > >
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [VOTE] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Really? I'm able to build it no problems. What's the error?
-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
Sent: Wednesday, July 04, 2007 10:59 PM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4
Compilation failure with 1.0-alpha-2-SNAPSHOT so cant try.
Vincent
2007/7/4, Brian E. Fox <br...@reply.infinity.nu>:
> Looks like an issue in the test tools. Can you try bumping the
> dependency back to 1.0-alpha-2-SNAPSHOT? It didn't seem to be required
> for me, but it's worth a shot.
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Wednesday, July 04, 2007 10:04 PM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> Hi Max,
>
> I confirm that it was on this tag. Here are the failing logs (Using
> maven 2.0.7):
>
http://people.apache.org/~vsiveton/maven-eclipse-plugin-2.4/target/suref
> ire-reports/
>
> It seems that target/maven-eclipse-plugin-test.jar was not build on
> solaris.
>
> Someone could confirm?
>
> Cheers,
>
> Vincent
>
> 2007/7/4, Max Bowsher <ma...@ukf.net>:
> > Vincent Siveton wrote:
> > > Same thing here:
> > > Tests work on windows, failed on solaris so -1 too
> >
> > Could you confirm what it was that you were building? Was it the
tag,
> >
>
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-
> 2.4/
> > ?
> >
> > If not, could you re-test, using that.
> >
> > If you're still getting errors, could you put the build logs
somewhere
> > downloadable?
> >
> > Thanks,
> > Max.
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4
Posted by Vincent Siveton <vi...@gmail.com>.
Compilation failure with 1.0-alpha-2-SNAPSHOT so cant try.
Vincent
2007/7/4, Brian E. Fox <br...@reply.infinity.nu>:
> Looks like an issue in the test tools. Can you try bumping the
> dependency back to 1.0-alpha-2-SNAPSHOT? It didn't seem to be required
> for me, but it's worth a shot.
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Wednesday, July 04, 2007 10:04 PM
> To: Maven Developers List
> Subject: Re: [VOTE] maven-eclipse-plugin 2.4
>
> Hi Max,
>
> I confirm that it was on this tag. Here are the failing logs (Using
> maven 2.0.7):
> http://people.apache.org/~vsiveton/maven-eclipse-plugin-2.4/target/suref
> ire-reports/
>
> It seems that target/maven-eclipse-plugin-test.jar was not build on
> solaris.
>
> Someone could confirm?
>
> Cheers,
>
> Vincent
>
> 2007/7/4, Max Bowsher <ma...@ukf.net>:
> > Vincent Siveton wrote:
> > > Same thing here:
> > > Tests work on windows, failed on solaris so -1 too
> >
> > Could you confirm what it was that you were building? Was it the tag,
> >
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-
> 2.4/
> > ?
> >
> > If not, could you re-test, using that.
> >
> > If you're still getting errors, could you put the build logs somewhere
> > downloadable?
> >
> > Thanks,
> > Max.
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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] maven-eclipse-plugin 2.4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Looks like an issue in the test tools. Can you try bumping the
dependency back to 1.0-alpha-2-SNAPSHOT? It didn't seem to be required
for me, but it's worth a shot.
-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
Sent: Wednesday, July 04, 2007 10:04 PM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4
Hi Max,
I confirm that it was on this tag. Here are the failing logs (Using
maven 2.0.7):
http://people.apache.org/~vsiveton/maven-eclipse-plugin-2.4/target/suref
ire-reports/
It seems that target/maven-eclipse-plugin-test.jar was not build on
solaris.
Someone could confirm?
Cheers,
Vincent
2007/7/4, Max Bowsher <ma...@ukf.net>:
> Vincent Siveton wrote:
> > Same thing here:
> > Tests work on windows, failed on solaris so -1 too
>
> Could you confirm what it was that you were building? Was it the tag,
>
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-
2.4/
> ?
>
> If not, could you re-test, using that.
>
> If you're still getting errors, could you put the build logs somewhere
> downloadable?
>
> Thanks,
> Max.
>
>
>
>
---------------------------------------------------------------------
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] maven-eclipse-plugin 2.4
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Max,
I confirm that it was on this tag. Here are the failing logs (Using
maven 2.0.7):
http://people.apache.org/~vsiveton/maven-eclipse-plugin-2.4/target/surefire-reports/
It seems that target/maven-eclipse-plugin-test.jar was not build on solaris.
Someone could confirm?
Cheers,
Vincent
2007/7/4, Max Bowsher <ma...@ukf.net>:
> Vincent Siveton wrote:
> > Same thing here:
> > Tests work on windows, failed on solaris so -1 too
>
> Could you confirm what it was that you were building? Was it the tag,
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.4/
> ?
>
> If not, could you re-test, using that.
>
> If you're still getting errors, could you put the build logs somewhere
> downloadable?
>
> Thanks,
> Max.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Max Bowsher <ma...@ukf.net>.
Vincent Siveton wrote:
> Same thing here:
> Tests work on windows, failed on solaris so -1 too
Could you confirm what it was that you were building? Was it the tag,
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.4/
?
If not, could you re-test, using that.
If you're still getting errors, could you put the build logs somewhere
downloadable?
Thanks,
Max.
Re: [VOTE] maven-eclipse-plugin 2.4
Posted by Vincent Siveton <vi...@gmail.com>.
Same thing here:
Tests work on windows, failed on solaris so -1 too
Cheers,
Vincent
2007/7/4, Kenney Westerhof <ke...@apache.org>:
> Update:
>
> It seems i was impatient, it took almost 3 minutes to run that single test.
> After that it continued (on 2.0.7), but I got a failure:
>
> -------------------------------------------------------------------------------
> Test set: org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest
> -------------------------------------------------------------------------------
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 39.878 sec <<< FAILURE!
> testModule1Project(org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest) Time elapsed: 11.979 sec <<< ERROR!
> org.apache.maven.plugin.eclipse.ExecutionFailedException: Failed to execute build.
> POM: /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/projects/master-test/pom.xml
> Goals: org.apache.maven.plugins:maven-eclipse-plugin:test:clean, org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse
> Exit Code: 1
> Error: null
> Build Log: file:/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports/build-output/org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest_testModule1Project.build.log
> (Resulting exit code: 1)
> at org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.executeMaven(AbstractEclipsePluginTestCase.java:309)
>
> Last part of the file:/ indicated above:
>
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
> at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562)
> ... 18 more
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 9 seconds
>
>
> btw, tests take about 7 minutes whereas bootstrapping maven itself takes only 3 minutes.
>
> my -1 stands, unless I'm the only one where this fails.
>
> -- Kenney
>
> Kenney Westerhof wrote:
> > I assume this is a vote to _release_ maven-eclipse-plugin 2.4.
> >
> > -1 until the tests are fixed:
> >
> >
> > [INFO] [surefire:test]
> > [INFO] Surefire report directory:
> > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports
> >
> >
> > -------------------------------------------------------
> > T E S T S
> > -------------------------------------------------------
> > Running org.apache.maven.plugin.eclipse.AddMavenRepoMojoTest
> > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.899 sec
> > Running
> > org.apache.maven.plugin.eclipse.writers.EclipseOSGiManifestWriterTest
> > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
> > Running org.apache.maven.plugin.eclipse.RadPluginTest
> > *** Running test builds; output will be directed to:
> > target/surefire-reports/build-output
> >
> > [INFO] Installing target/maven-eclipse-plugin-test.jar to
> > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.jar
> >
> > [INFO] Installing ../pom.xml to
> > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-plugins/9-SNAPSHOT/maven-plugins-9-SNAPSHOT.pom
> >
> > [INFO] Installing ../../pom/maven/pom.xml to
> > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/maven-parent/6-SNAPSHOT/maven-parent-6-SNAPSHOT.pom
> >
> > [INFO] Installing ../../pom/maven/../asf/pom.xml to
> > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/apache/5-SNAPSHOT/apache-5-SNAPSHOT.pom
> >
> > *** Installed test-version of the Eclipse plugin to:
> > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo
> >
> >
> > and it indefinitely hangs at this point, no cpu load.
> >
> >
> > Tested with maven 2.1 and 2.0.7.
> > Otherwise the plugin works great.
> >
> > -- Kenney
> >
> > Brian E. Fox wrote:
> >> It's been about 5 months since an eclipse plugin release and we have
> >> lots of fixes and a handful of enhancements:
> >>
> >> Bug
> >> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> >> javax.servlet:servlet-api:2.3
> >> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear
> >> packaging
> >> * [MECLIPSE-151] - Incorrect name for test sources jars
> >> * [MECLIPSE-198] - EJB version is not resloved
> >> * [MECLIPSE-215] - WTP 1.5 Documentation
> >> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> >> eclipse:eclipse for war and ejb projects.
> >> * [MECLIPSE-225] - Invalid .classpath Entries.
> >> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> >> case-sensitive
> >> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> >> String method argument causing maven-eclipse.xml copy-resources problems
> >> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> >> resolution:=optional directive
> >> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> >> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
> >> wtp facet
> >> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
> >> to be built
> >> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> >> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
> >> in pom.xml
> >> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> >> Java 5.0 project
> >> * [MECLIPSE-278] - duplicated classpathentries
> >> * [MECLIPSE-279] - PDE projects should be considered java projects in
> >> all cases
> >> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> >> containing dependencies with classifiers
> >> Improvement
> >> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> >> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> >> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> >> version, jsp version, ... possible through pom configuration
> >> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> >> creation while executing eclipse:rad
> >> New Feature
> >> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> >> * [MECLIPSE-189] - addVersionToProjectName property
> >> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> >> * [MECLIPSE-271] - Ability to skip
> >>
> >> The site has been updated:
> >> http://maven.apache.org/plugins/maven-eclipse-plugin
> >>
> >> Plugin is staged here:
> >> http://people.apache.org/~brianf/staging-repository/
> >>
> >> Vote is open for 72hrs.
> >>
> >> +1
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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] maven-eclipse-plugin 2.4
Posted by Kenney Westerhof <ke...@apache.org>.
Update:
It seems i was impatient, it took almost 3 minutes to run that single test.
After that it continued (on 2.0.7), but I got a failure:
-------------------------------------------------------------------------------
Test set: org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest
-------------------------------------------------------------------------------
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 39.878 sec <<< FAILURE!
testModule1Project(org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest) Time elapsed: 11.979 sec <<< ERROR!
org.apache.maven.plugin.eclipse.ExecutionFailedException: Failed to execute build.
POM: /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/projects/master-test/pom.xml
Goals: org.apache.maven.plugins:maven-eclipse-plugin:test:clean, org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse
Exit Code: 1
Error: null
Build Log: file:/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports/build-output/org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest_testModule1Project.build.log
(Resulting exit code: 1)
at org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.executeMaven(AbstractEclipsePluginTestCase.java:309)
Last part of the file:/ indicated above:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin'
at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugin:test:eclipse.
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562)
... 18 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9 seconds
btw, tests take about 7 minutes whereas bootstrapping maven itself takes only 3 minutes.
my -1 stands, unless I'm the only one where this fails.
-- Kenney
Kenney Westerhof wrote:
> I assume this is a vote to _release_ maven-eclipse-plugin 2.4.
>
> -1 until the tests are fixed:
>
>
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports
>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.maven.plugin.eclipse.AddMavenRepoMojoTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.899 sec
> Running
> org.apache.maven.plugin.eclipse.writers.EclipseOSGiManifestWriterTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
> Running org.apache.maven.plugin.eclipse.RadPluginTest
> *** Running test builds; output will be directed to:
> target/surefire-reports/build-output
>
> [INFO] Installing target/maven-eclipse-plugin-test.jar to
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.jar
>
> [INFO] Installing ../pom.xml to
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-plugins/9-SNAPSHOT/maven-plugins-9-SNAPSHOT.pom
>
> [INFO] Installing ../../pom/maven/pom.xml to
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/maven-parent/6-SNAPSHOT/maven-parent-6-SNAPSHOT.pom
>
> [INFO] Installing ../../pom/maven/../asf/pom.xml to
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/apache/5-SNAPSHOT/apache-5-SNAPSHOT.pom
>
> *** Installed test-version of the Eclipse plugin to:
> /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo
>
>
> and it indefinitely hangs at this point, no cpu load.
>
>
> Tested with maven 2.1 and 2.0.7.
> Otherwise the plugin works great.
>
> -- Kenney
>
> Brian E. Fox wrote:
>> It's been about 5 months since an eclipse plugin release and we have
>> lots of fixes and a handful of enhancements:
>>
>> Bug
>> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
>> javax.servlet:servlet-api:2.3
>> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear
>> packaging
>> * [MECLIPSE-151] - Incorrect name for test sources jars
>> * [MECLIPSE-198] - EJB version is not resloved
>> * [MECLIPSE-215] - WTP 1.5 Documentation
>> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
>> eclipse:eclipse for war and ejb projects.
>> * [MECLIPSE-225] - Invalid .classpath Entries.
>> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
>> case-sensitive
>> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
>> String method argument causing maven-eclipse.xml copy-resources problems
>> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
>> resolution:=optional directive
>> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
>> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
>> wtp facet
>> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
>> to be built
>> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
>> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
>> in pom.xml
>> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
>> Java 5.0 project
>> * [MECLIPSE-278] - duplicated classpathentries
>> * [MECLIPSE-279] - PDE projects should be considered java projects in
>> all cases
>> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
>> containing dependencies with classifiers
>> Improvement
>> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
>> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
>> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
>> version, jsp version, ... possible through pom configuration
>> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
>> creation while executing eclipse:rad
>> New Feature
>> * [MECLIPSE-119] - Allow custom project name for eclipse projects
>> * [MECLIPSE-189] - addVersionToProjectName property
>> * [MECLIPSE-251] - Allows prefixing of eclipse project name
>> * [MECLIPSE-271] - Ability to skip
>>
>> The site has been updated:
>> http://maven.apache.org/plugins/maven-eclipse-plugin
>>
>> Plugin is staged here:
>> http://people.apache.org/~brianf/staging-repository/
>>
>> Vote is open for 72hrs.
>>
>> +1
>>
>>
>> ---------------------------------------------------------------------
>> 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] maven-eclipse-plugin 2.4
Posted by Kenney Westerhof <ke...@apache.org>.
I assume this is a vote to _release_ maven-eclipse-plugin 2.4.
-1 until the tests are fixed:
[INFO] [surefire:test]
[INFO] Surefire report directory: /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.maven.plugin.eclipse.AddMavenRepoMojoTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.899 sec
Running org.apache.maven.plugin.eclipse.writers.EclipseOSGiManifestWriterTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
Running org.apache.maven.plugin.eclipse.RadPluginTest
*** Running test builds; output will be directed to: target/surefire-reports/build-output
[INFO] Installing target/maven-eclipse-plugin-test.jar to /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-eclipse-plugin/test/maven-eclipse-plugin-test.jar
[INFO] Installing ../pom.xml to /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-plugins/9-SNAPSHOT/maven-plugins-9-SNAPSHOT.pom
[INFO] Installing ../../pom/maven/pom.xml to /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/maven/maven-parent/6-SNAPSHOT/maven-parent-6-SNAPSHOT.pom
[INFO] Installing ../../pom/maven/../asf/pom.xml to /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo/org/apache/apache/5-SNAPSHOT/apache-5-SNAPSHOT.pom
*** Installed test-version of the Eclipse plugin to: /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-plugin/target/test-classes/m2repo
and it indefinitely hangs at this point, no cpu load.
Tested with maven 2.1 and 2.0.7.
Otherwise the plugin works great.
-- Kenney
Brian E. Fox wrote:
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements:
>
> Bug
> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> javax.servlet:servlet-api:2.3
> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear
> packaging
> * [MECLIPSE-151] - Incorrect name for test sources jars
> * [MECLIPSE-198] - EJB version is not resloved
> * [MECLIPSE-215] - WTP 1.5 Documentation
> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn
> eclipse:eclipse for war and ejb projects.
> * [MECLIPSE-225] - Invalid .classpath Entries.
> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> case-sensitive
> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses
> String method argument causing maven-eclipse.xml copy-resources problems
> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> resolution:=optional directive
> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in
> wtp facet
> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server
> to be built
> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test"
> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined
> in pom.xml
> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a
> Java 5.0 project
> * [MECLIPSE-278] - duplicated classpathentries
> * [MECLIPSE-279] - PDE projects should be considered java projects in
> all cases
> * [MECLIPSE-287] - Regression - fails to correctly construct classpath
> containing dependencies with classifiers
> Improvement
> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet
> version, jsp version, ... possible through pom configuration
> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> creation while executing eclipse:rad
> New Feature
> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> * [MECLIPSE-189] - addVersionToProjectName property
> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> * [MECLIPSE-271] - Ability to skip
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/staging-repository/
>
> Vote is open for 72hrs.
>
> +1
>
>
> ---------------------------------------------------------------------
> 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