On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
It pulls that artifact from your project's plugin repositories, based on
the assumption that that is where the surefire plugin from.
Since you built from source, that assumption isn't right. You'll have to
build the other from source.
Thanks f
It pulls that artifact from your project's plugin repositories, based on
the assumption that that is where the surefire plugin from.
Since you built from source, that assumption isn't right. You'll have to
build the other from source.
- Brett
Brett Porter wrote:
You need to build install su
You need to build install surefire first.
However, it should have attempted to look for this on the snapshot repo
- I'll look into it.
- Brett
Wendy Smoak wrote:
I just updated built maven-surefire-plugin 2.2-SNAPSHOT from source,
then tried 'mvn test' on my own project.
I get:
[INFO]
I just updated built maven-surefire-plugin 2.2-SNAPSHOT from source,
then tried 'mvn test' on my own project.
I get:
[INFO]
[ERROR] BUILD ERROR
[INFO]
I'm on windows :)
I'll try a clean checkout.
- Brett
dan tran wrote:
I am able to reproduce same test failures on another windows ( 2003 ) with
maven-2.0.4.
No one on widnows attempts to build latest release plugin source?
On 5/9/06, dan tran <[EMAIL PROTECTED]> wrote:
I am on XP
-D
I am able to reproduce same test failures on another windows ( 2003 ) with
maven-2.0.4.
No one on widnows attempts to build latest release plugin source?
On 5/9/06, dan tran <[EMAIL PROTECTED]> wrote:
I am on XP
-D
On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> what operating sy
I am on XP
-D
On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
what operating system? Looks like line ending issues in the tests.
These seem minor. It's probably one failure that affects all those tests.
- Brett
dan tran wrote:
> here you go
>
> Results :
> Tests run: 260, Failures: 48,
After testing with the correct version of the plugin, a huge +1 from me.
I was only able to find one minor issue
(http://jira.codehaus.org/browse/SCM-197) everything else seemed perfect
on my large 20 module build.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tu
Grrr. I started testing on one project and then moved to another one and
forgot to move the version to the new one. I can't believe I wasted all
that time thoroughly documenting the original version! C'est la vie.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tues
Sorry sorry. You're using 2.0-beta-3 or an older version of beta-4. You
should be able to confirm via mvn help:describe -Dplugin=release
The release is indeed beta-4, not beta-5, and the snapshot you list is
correct. But you are definitely not using that one from the output you had.
- Brett
I'm confused. A previous email said "2.0-beta-4-20060509.101136-3 was
the version and the subject was wrong.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 7:40 PM
To: Maven Developers List
Subject: Re: [vote] Release Release plugin 2.0-beta-5
You need to add the group,arifcatId and version to the
dependencyManagement section of a parent.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of David Smiley
Sent: Tuesday, May 09, 2006 4:19 PM
To: m2-dev@maven.apache.org
Subject: inheritance
http://maven.apache.org/
+1 as long as this doesn't break previous builds
On 5/3/06, Brett Porter <[EMAIL PROTECTED]> wrote:
It seems to be common to hit XML problems with surefire because it is
using child first classloading (like a webapp) to ensure you get what
you ask for which often causes xml problems because the
I've omitted some responses as it all comes down to one thing.
Brian E. Fox wrote:
2. would be nice if I could say use the same version for all in a
multiproject build
Please file it for 2.0.
5. the new development version default is empty: [INFO] What is the new
development version for 'tes
release:perform does "deploy site-deploy" by default.
- Brtt
Brian E. Fox wrote:
Still testing, but here's my initial observation: it looks like
release:perform is doing a compile. If this is the first time this
version has been built, it will fail in a multi project because sibling
dependencie
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
At the above page, there is an example of modules specifying
dependencies without a version. The version is fully specified by the
parent. Okay, that's nice. But it just doesn't work for me. I get
these e
what operating system? Looks like line ending issues in the tests.
These seem minor. It's probably one failure that affects all those tests.
- Brett
dan tran wrote:
here you go
Results :
Tests run: 260, Failures: 48, Errors: 0, Skipped: 0
One of those test is in
Running
org.apache.maven.plu
+1
Jesse McConnell wrote:
I would like to call a vote to release the maven-resources-plugin
version 2.2
+1 []
0 []
-1 []
the following issues were resolved for the release of this plugin...
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12486&styleName=Text&projectId=11145&Create=
+1
-Original Message-
From: Jesse McConnell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 4:29 PM
To: Maven Developers List
Subject: [VOTE] release maven-resources-plugin 2.2
I would like to call a vote to release the maven-resources-plugin
version 2.2
+1 []
0 []
-1 []
the f
I would like to call a vote to release the maven-resources-plugin version 2.2
+1 []
0 []
-1 []
the following issues were resolved for the release of this plugin...
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12486&styleName=Text&projectId=11145&Create=Create
Release Notes - Mave
if you need help about using maven, the best place is
"users@maven.apache.org" - this mailing list is for the maven
developers (although I'm a maven dev ;-)
see http://maven.apache.org/mail-lists.html for a list of available
mailing list.
cheers...
On 5/9/06, Leo L <[EMAIL PROTECTED]> wrote:
Hi,
I have a NullPointerException with de plugin statcvs and I don´t known how
to solve it...
My pom.xml is like this
${basedir}\src
maven-checkstyle-plugin
log4j
log4j
1.2.12
No, it is not synced, and we don't put snapshots. If you want 1.1_02
there, please make sure everything is right (pom included) and tell me
where to get it. Is Sun's implementation the reference one?
On 5/5/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Looks like JSF 1.1 has been released under the C
That would be great, do you volunteer? ;)
On 5/7/06, jerome lacoste <[EMAIL PROTECTED]> wrote:
On 5/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm noticing several files cropping up again with no svn:eol-style set.
> The tell-tale sign is when you commit something and every line cha
Hi,
I'd like to release the following plugins for inclusion in maven-1.1-beta-3:
[] maven-antlr-plugin-1.2.2
[] maven-cruisecontrol-plugin-1.8
I am not using either of them so I'd appreciate someone do some testing.
For changes please check the jira and changes reports on the
stage sites given
Weird, I though I voted for this one and I can't find it in my sent items.
+1
s/
On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
based on:
maven-idea-plugin 2.0-20060509.134930-1 (r405319)
[ ] +1
[ ] +0
[ ] -1
The documentation is small, but its a self-explanatory plugin. The
fields are
Hey Lukas,
No problem, I just though that it was a good time to release. We will
discuss on IRC, I'll try to connect later today.
Regarding your questions:
* You're right, will fix this one
* Regarding the manifest creation, we have the same kind of issues in M2
(manifests created by M2 are not
Sorry to spoil the party but it's -1 from me for now. Could you
clarify/comment on the following points:
* Why did MPWAR-52 get fixed but not MPWAR-49? It's basically the same
requirement (and MPWAR-34 is a dupe btw).
* There are a number of issues open concerning the manifest creation
(MPWA
+1 x2
Just some comments on the ant plugin:
* there is a layout problem in the table of the properties page
(maven.ant.excludeTests)
* there is an issue with m1.0 compatibility: running maven genapp - ant
- ant:execute fails on m1.0.2 because junit classes cannot be found. I
suppose it's be
Some more observations:
1. It failed on pom checkin because my username was wrong (forgot
-Dusername=). After rerunning this with the correct parameter, it failed
because it tried to do a straight compile again (mentioned below).
Shouldn't it have known from the release.properties that it was alre
On 5/9/06, Vincent Massol <[EMAIL PROTECTED]> wrote:
Yeah!
+1
+99
J
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
here you go
Results :
Tests run: 260, Failures: 48, Errors: 0, Skipped: 0
One of those test is in
Running
org.apache.maven.plugins.release.phase.RewritePomsForDevelopmentPhaseTe
t
Tests run: 39, Failures: 22, Errors: 0, Skipped: 0, Time elapsed: 6.266 sec
<<<
FAILURE!
Test set:
org.apache.mav
Why would you complain about an error but NOT attach the error itself?
I get this error when I try to run the release tests:
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.maven.surefire:surefire-junit:jar:2.0-SNAPSHOT
Try downloading the file manually from the project w
I am having test failures in latest release plugin, does any one encounter
this?
or it is just me!!
-Dan
I disagree. They are all part of the EJB spec. IMO it's better to have
a more-sophisticated ejb-plugin than to scatter the spec over two or
three plugins...
If the two plugins still seems more appropriate, then both plugins
should be renamed: 1) maven-ejb-sessions-plugin, and 2)
maven-ejb-entitie
Still testing, but here's my initial observation: it looks like
release:perform is doing a compile. If this is the first time this
version has been built, it will fail in a multi project because sibling
dependencies can't be found. Is there a reason not to do install?
-Original Message-
F
Yeah!
+1
-Vincent
> -Original Message-
> From: Jesse McConnell [mailto:[EMAIL PROTECTED]
> Sent: mardi 9 mai 2006 16:43
> To: Maven Developers List
> Subject: Re: [vote] Release Maven IDEA Plugin 2.0
>
> definite +1
>
> On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> >
> > based o
+1
Emmanuel
Jesse McConnell a écrit :
definite +1
On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
based on:
maven-idea-plugin 2.0-20060509.134930-1 (r405319)
[ ] +1
[ ] +0
[ ] -1
The documentation is small, but its a self-explanatory plugin. The
fields are well documented, but the plug
definite +1
On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
based on:
maven-idea-plugin 2.0-20060509.134930-1 (r405319)
[ ] +1
[ ] +0
[ ] -1
The documentation is small, but its a self-explanatory plugin. The
fields are well documented, but the plugin report output still needs
some work whi
based on:
maven-idea-plugin 2.0-20060509.134930-1 (r405319)
[ ] +1
[ ] +0
[ ] -1
The documentation is small, but its a self-explanatory plugin. The
fields are well documented, but the plugin report output still needs
some work which can then be used to republish later.
http://jira.codehaus.o
Allison, Bob wrote:
+0 from this user.
A few changes I would like to see:
-- When running the project to verify that everything works correctly,
it would be nice if batch mode was used. The first time I ran this, it
decided to update a few plugins and I got a lot of 1/100K, 2/100K, ...
lines d
+0 from this user.
A few changes I would like to see:
-- When running the project to verify that everything works correctly,
it would be nice if batch mode was used. The first time I ran this, it
decided to update a few plugins and I got a lot of 1/100K, 2/100K, ...
lines displayed.
-- It would
+1
Thanks for the work on this, Brett.
-john
On 5/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
That's a good point. I assume the release plugin should be able to be
excluded from the dependency checks. I'll make that change.
- Brett
Allison, Bob wrote:
> It looks like a catch-22 to test th
That's a good point. I assume the release plugin should be able to be
excluded from the dependency checks. I'll make that change.
- Brett
Allison, Bob wrote:
It looks like a catch-22 to test this.
If I update the plugin configuration so I use the 2.0-beta-4-SNAPSHOT
version of the release plu
Richard van der Hoff wrote:
On the other hand, it means I now need to set up my assembly such that
the zip files are unpacked. Ideally, I'd like for all such artifacts to
be unpacked automatically, but there doesn't seem to be any way of doing
so without configuring it in each assembly.xml. It'
It looks like a catch-22 to test this.
If I update the plugin configuration so I use the 2.0-beta-4-SNAPSHOT
version of the release plugin, release:prepare fails because I depend on
a snapshot version of a plugin.
If I change the version number to "2.0-beta-4-20060509.101136-3" (or
"2.0-beta-4-20
Ideally, yes (that was also under a release vote, but a last minute
problem has been found).
It doesn't affect it's execution, just the build. It will build with an
old version, but you need to bump up the memory allocated due to the
surefire memory leak. I think fork = pertest might work too.
I tried building the plugin from source but it depends on a snapshot
version of the surefire plugin. Does that need to be fixed before this
can be released?
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 07:57
To: Maven Developers List
Subject
Sorry again. We recently were able to set up a snapshot repository at
Apache and I hadn't updated the docs. Done now. It's at:
http://svn.apache.org/maven-snapshot-repository
Cheers,
Brett
Allison, Bob wrote:
OK, I am probably doing something wrong.
I go to the "Guide to Testing Development
OK, I am probably doing something wrong.
I go to the "Guide to Testing Development Versions of Plugins" page and
click on the link to development versions (I am already suspicious
because it is at codehaus rather than apache). I navigate to
org/apache/maven/plugins/maven-release-plugin/2.0-beta-4
Hi all,
Apologies in advance for the length of this mail. As you'll see, I've
been thinking about this for a while, but I want to get it right first
time rather than end up supporting legacy builds in the future. I'm
looking for suggestions on how best to handle native libraries. We have
quit
Sorry, it's:
2.0-beta-4-20060509.101136-3
(the subject line is incorrect)
Allison, Bob wrote:
Is there a snapshot to use (if so, what is the URL?) or do I need to
build from SVN?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 20:19
To: Mav
Is there a snapshot to use (if so, what is the URL?) or do I need to
build from SVN?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 20:19
To: Maven Developers List
Subject: [vote] Release Release plugin 2.0-beta-5
No, that's not a typo.
I'd l
+1
Emmanuel
Brett Porter a écrit :
No, that's not a typo.
I'd like to vote to release the release plugin. It has been completely
rewritten since you last met it and now has over 250 unit tests covering
everything. Nearly all of the JIRA issues have been closed - a select
few were deferred t
+1
Emmanuel
Stephane Nicoll a écrit :
Hi,
I'd like to call a vote to release the 2.2 version of maven-ear-plugin.
There is only one issue left in the MEAR project and I need feedback to
resolve it.
You can test against maven-ear-plugin-2.2-2060508.184604-1.jar, the staging
site is available a
+1
Emmanuel
John Casey a écrit :
Hi,
I'd like to call a vote to release the 2.1 version of
maven-assembly-plugin.
Remember, please test this plugin before voting, if possible.
Revision: 405096
Snapshot Version: 2.1-20060508.163042-8
We've fixed several issues and added a few features for t
Hi,
+1 (user vote, happy user ;-) )
I have made a lot tests with a test case included in
http://jira.codehaus.org/browse/MRELEASE-103.
I don't understand why I need to set the -DconnectionUrl because this
should be picked up from developerConnection setted in the root pom ?
- Olivier
-Messag
57 matches
Mail list logo
