The plugin testing tools had a bug that caused the real build artifacts
to become corrupted with the IT test version. This release is required
for the eclipse-plugin 2.4 release.
Issues fixed:
MNG-3095 : maven-plugin-testing-tools causes bad version in deployed
artifacts after tests are run
MECLIP
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
Tell me about it. I finally have it resolved...standby for an updated
snapshot ;-)
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 9:03 PM
To: Maven Developers List
Subject: Re: CANCELLED: [VOTE] maven-eclipse-plugin 2.4
brianf < debugger of t
brianf < debugger of the day :-)
-D
On 7/6/07, Carlos Sanchez <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote:
On 06/07/07, John Casey <[EMAIL PROTECTED]> wrote:
t looks like this has broken the trunk build. I get compiler errors now:
[java] /Users/jdcasey/workspace/maven/components/maven-artifact/
src/test/java/org/apache/maven/artifact/resolver/
DefaultArtifactCollectorTest.java:[674,25] cannot f
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 <[EMAIL PROTECTED]> wrote:
Despite my best efforts to deny it ;-) The eclipse 2.4 stage is bad.
Somehow the /WEB-INF/plugin
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
maven-osgi is a shared library for maven to osgi and viceversa common
code, like version conversion. It's used by the felix bundle plugin
and the eclipse plugin.
https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-osgi
Tagged in https://svn.apache.org/repos/asf/maven/shared/tags/ma
t looks like this has broken the trunk build. I get compiler errors now:
[java] /Users/jdcasey/workspace/maven/components/maven-artifact/
src/test/java/org/apache/maven/artifact/resolver/
DefaultArtifactCollectorTest.java:[674,25] cannot find symbol
[java] symbol : method createArtif
'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 <[EMAIL PROTECTED]> wrote:
set the version in the pom or run somet
I've added MECLIPSE-295 and a test case, please give it a try
On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
2.4 works fine when I get it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Friday, July 06, 2007 11:58 AM
To: Maven
On 7/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: jvanzyl
Date: Fri Jul 6 09:34:35 2007
New Revision: 553946
URL: http://svn.apache.org/viewvc?view=rev&rev=553946
Log:
o getting the initial code moved over, i'll work on it here with anyone who
wants to help repackage it
Accordi
The Apache Maven team would like to announce the availability of the
Maven Ant Tasks 2.0.7.
You can find the binaries here:
http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-
tasks-2.0.7.jar
You can find the release notes here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
2.4 works fine when I get it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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 so
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:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 11:50 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-ecli
Sorry for the late reply, Maven traffic is a bit to much for me. I did want
to chime in though that I think the CXF build gives a real good example of
how to use the Shade plugin:
http://fisheye6.cenqua.com/browse/celtixfire/trunk/distribution/bundle/pom.xml?r=HEAD
I also wrote a custom transfor
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 <[EMAIL PROTECTED]> 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 specifical
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:ec
That sounds like a fine idea to me. I commented on the issue, too, fwiw.
Thanks,
-john
On Jul 6, 2007, at 5:55 AM, Fabrice Bellingard wrote:
I got this problem while trying to make an assembly, with filtered
files,
from a root project. I created an issue on JIRA with an example:
http://jir
+1
Emmanuel
John Casey a écrit :
Hi all,
Jesse and I have been working on a patch plugin that I migrated over
from mojo.codehaus.org into the ASF sandbox, and we feel it's ready for
a release. I've prepared the documentation for a code grant on this
project, and all the appropriate informat
+1
would like to note, that the first version would be useful on
pre-shaded maven versions using p-u 1.1 and we have it ready to
release again using later versions of p-u and the maven 2.0.6+
versions that will have more bullet proof bash shell support.
On 7/6/07, John Casey <[EMAIL PROTECTED]>
+1
On 6 Jul 07, at 8:08 AM 6 Jul 07, John Casey wrote:
Hi all,
Jesse and I have been working on a patch plugin that I migrated
over from mojo.codehaus.org into the ASF sandbox, and we feel it's
ready for a release. I've prepared the documentation for a code
grant on this project, and all
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:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 10:41 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CUR
Hi all,
Jesse and I have been working on a patch plugin that I migrated over
from mojo.codehaus.org into the ASF sandbox, and we feel it's ready
for a release. I've prepared the documentation for a code grant on
this project, and all the appropriate information should be committed
in the
Hi guys,
I'm playing a bit with the maven site plugin to see what's left before it
gets released. However, I have a problem with the site.xml inheritance when
building multimodule projects: whether I define a site.xml file in
submodules or not, the site plugin always uses the site.xml of the root
Thanks for the follow up Brett.
An issue already exists:
http://jira.codehaus.org/browse/MJAVADOC-127
Cheers,
Vincent
2007/7/5, Brett Porter <[EMAIL PROTECTED]>:
(mainly for Vincent who was asking)
I've fixed the problem with the tests failing on Solaris due to the
© entity (still don't unde
mvn eclipse:eclipse -P brianf-repo
I use brianf-repo profile to pickup 2.4
-D
On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> 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-
Forgive my ignorance of the subject line conventions
of this mailing list, and please note in advance that
I personally am not subscribed to any Maven lists (I
believe Kevin Jackson is subscribed to one or more of
them). At any rate, it has come to the attention of
the Ant developers that Maven's
Hi,
There's only one remaining issue, MRELEASE-83, scheduled for
2.0-beta-7 - is anyone likely to work on this soon, or shall we defer
it until beta-8? I would like to see beta-7 released for the release
POM fixes - they're rather unusable in beta-6.
Cheers,
Mark
-
For now, I'm a fan of disallowing snapshots when they are not explicitly in
the boundary, as per the patch.
In my mind, the problem with a profile flag is that it's an all-or-nothing
proposition. Any released artifacts with version ranges will also start to
pull in snapshots. There wouldn't be
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
eclispe-plugin 2.3 works fine. The problem is in the unreleased eclipse-2.4
-Dan
On 7/6/07, Brian E. Fox <[EMAIL PROTECTED]> 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:[EMAIL PRO
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:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 9:54 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-eclipse-plugin 2.4 (CURRENT SUMMARY)
One mo
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 <[EMAIL PROTECTED]> wro
Hi,
Whilst attempting to fix MNG-2994, I discovered MNG-3092 that was
contrary to the 2.0 design docs:
http://jira.codehaus.org/browse/MNG-3092
Brett, Kenney and myself had a brief discussion on IRC about this:
Kenney says that the behaviour is theoretically correct (which it is),
although I fe
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:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 1:
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 wi
I got this problem while trying to make an assembly, with filtered files,
from a root project. I created an issue on JIRA with an example:
http://jira.codehaus.org/browse/MASSEMBLY-226
If the "filters" parameter would not be readonly, then this bug would be
obsolete.
Should I modify this? I ask t
Sorry if I'm posting to the wrong list here.
I've been working on this for several days now with no solution coming
out.
The test works from within a Maven context, but when run it as a
stand-alone test from within Eclipse the following stack trace is
produced.
The Plexus look-up method
39 matches
Mail list logo
