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/07 02:22:35 UTC
CANCELLED: [VOTE] maven-eclipse-plugin 2.4
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: 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