Hi,
Sorry for the insistence, but could someone have a look at my patch for
MASSEMBLY-561. John Casey started to look at the patch but seems he is busy. We
have users that are forced to use a custom released version of m-assembly-p and
I wouldn’t like this situation to stay as it is.
Thanks
On Mon, 26 Sep 2011 17:26:06 -0500
Paul Gier pg...@apache.org wrote:
+1 (non binding)
Works fine for your projects.
Tony.
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17431
There are still lots of issues left in JIRA:
+1
On Tue, Sep 27, 2011 at 12:26 AM, Paul Gier pg...@apache.org wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17431
There are still lots of issues left in JIRA:
+1
On Mon, Sep 26, 2011 at 3:56 PM, Olivier Lamy ol...@apache.org wrote:
Hello,
I'd like to release Apache Maven Wagon 2.0.
We fixed 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create
Staging repo :
On Mon, 26 Sep 2011 15:56:23 +0200
Olivier Lamy ol...@apache.org wrote:
+1 (non binding)
Thanks,
Tony.
Hello,
I'd like to release Apache Maven Wagon 2.0.
We fixed 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create
Staging
+1
2011/9/27 Paul Gier pg...@apache.org:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17431
There are still lots of issues left in JIRA:
Reposting to an old thread, since I am still running into what seems to be
Maven 2 debris in the APIs.
On 11/19/2010 02:19 PM, Kristian Rosenvold wrote:
if it hurts you, make a patch; documentation upgrade, javadoc or code changes
The difficulty with submitting Javadoc changes is that if you
+1
Emmanuel
On Tue, Sep 27, 2011 at 12:26 AM, Paul Gier pg...@apache.org wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17431
There are still lots of issues left in JIRA:
+1
Emmanuel
On Mon, Sep 26, 2011 at 3:56 PM, Olivier Lamy ol...@apache.org wrote:
Hello,
I'd like to release Apache Maven Wagon 2.0.
We fixed 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create
Staging repo :
Is it a known issue that the release plugin does not honor the -Darguments?
Specifically, I'm attempting to:
mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true
-DfailIfNoTests=false
It takes 40 minutes to get through a dryRun with tests on. We still have
several kinks in the
I need change version of a dependency but I can`t find a way to not depend on
the Dependency`s oldVersion. I have:
dependencyManagement
dependencies
...
dependency
groupIdcom.legi.info/groupId
artifactIdMRKartifactId
On Tue, Sep 27, 2011 at 07:49:37AM -0400, Jesse Glick wrote:
On 11/19/2010 02:19 PM, Kristian Rosenvold wrote:
if it hurts you, make a patch; documentation upgrade, javadoc or code
changes
The difficulty with submitting Javadoc changes is that if you need
the Javadoc you probably are not
Hi community,
I'm using : apache-maven-3.0.3 , hudson-2.1.1 but i'm having this error
during building my project
Démarré par l'utilisateur anonymous Updating
file:///C:/SVNRepository/mavenhudsonproject revision: 27 sept. 2011 14:14:49
depth:infinity ignoreExternals: false At revision 6 Found
There is also http://jira.codehaus.org/browse/MNG-4996 , which might be
one of the problems you have. Unfortunately I have not been able to
reproduce this on any medium-sized or small project that I have
available, it only seems to happen on the really large ones.
(The reason for this probably
I am wondering about what kind of documentation you are thinking about.
We have so much documentation that I hardly know where to stop.
I think blind javadoc is just so much baloney. If there are any
specific use cases that require documentation I'm happy to discuss
that.
Kristian
ti.,
I noticed some possible problems in the staged site docs. The maven
failsafe plugin no longer generates a site, and the shadefire JUnit 3
provider also doesn't have a site.
Looks like the site configuration was removed from the failsafe plugin
[1], and the parent relationship was changed for
shadefire should not have a site, it's an entirely private artifact in
the surefire build, basically a shaded previous version of surefire to
run the tests for surefire itself.
Stephen did the site work and I'm sure he can tell us what's up ;)
Kristian
ti., 27.09.2011 kl. 09.12 -0500, skrev
Hmmm the site was being generated for 2.9...
Paul,
What version of maven did you stage the docs with?
-Stephen
On 27 September 2011 15:24, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
shadefire should not have a site, it's an entirely private artifact in
the surefire build,
You should have see something like this when runing mvn site
[INFO]
[INFO] Building Maven Surefire Plugin 2.11-SNAPSHOT
[INFO]
[INFO]
*[INFO] ---
On 27 Sep 2011, at 14:39, Amiragl amy...@live.fr wrote:
Hi community,
I'm using : apache-maven-3.0.3 , hudson-2.1.1 but i'm having this error
during building my project
Looks like http://issues.hudson-ci.org/browse/HUDSON-9004
This will be fixed in 2.1.2 (expected soon) otherwise you could
Thank you for the responce , I'll try 2.1.0 until the release of 2.1.2 on 30
september :) it's soon
Date: Tue, 27 Sep 2011 08:51:35 -0700
From: ml-node+s40175n4845847...@n5.nabble.com
To: amy...@live.fr
Subject: Re: problem to build maven 3 project from hudson console
On 27 Sep
The only problem is that a link for Shadefire still shows up as one of
the modules of surefire. For now, should I just hack the HTML to remove
this link?
http://maven.apache.org/surefire-2.10/
On 09/27/2011 09:24 AM, Kristian Rosenvold wrote:
shadefire should not have a site, it's an entirely
I ran mvn site:site instead of following the directions like I was
supposed to ;)
The failsafe plugin staging URL now looks good (pending sync).
http://maven.apache.org/plugins/maven-failsafe-plugin-2.10/
On 09/27/2011 09:36 AM, Stephen Connolly wrote:
You should have see something like this
+1 -Robert
Date: Tue, 27 Sep 2011 14:13:02 +0200
Subject: Re: [VOTE] Release Apache Maven Wagon 2.0
From: emmanuel.veni...@gmail.com
To: dev@maven.apache.org
+1
Emmanuel
On Mon, Sep 26, 2011 at 3:56 PM, Olivier Lamy ol...@apache.org wrote:
Hello,
I'd like to release Apache
IIRC you have to include your forked maven arguments in the release plugin
configuration under
arguments-DskipTests=true -DfailIfNoTests=false/arguments
Perhaps someone else can say _why_ the m-r-p is set up so you can't set this on
the command line?
thanks
david jencks
On Sep 27, 2011, at
you can if you understand shell escaping.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 27 Sep 2011 17:58, David Jencks david_jen...@yahoo.com wrote:
IIRC you have to
Hi,
I've checked out the sources and ran all tests first. On my machine the IT for
massemble-196 is failing.
So I first have to figure out what's going on here before I can continue on
your issue.
Maybe someone else could pick it up in the meantime.
-Robert
Date: Tue, 27 Sep 2011
+1
Hervé
Le lundi 26 septembre 2011, Olivier Lamy a écrit :
Hello,
I'd like to release Apache Maven Wagon 2.0.
We fixed 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=T
extprojectId=10335Create=Create
Staging repo :
+1
Hervé
Le mardi 27 septembre 2011, Paul Gier a écrit :
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17
431
There are still lots of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejq
That's not it, the quoting was fine. Even with a single argument with no
spaces to -Darguments it still does not work.
Did some more digging and it seems the issue is in the apache-10 parent pom.
If you alter it like so, the arguments are passed as expected:
plugin
30 matches
Mail list logo
