Sorry maven guys, It was for this mailing list.
cheers
Arnaud
On Wed, Dec 24, 2008 at 7:46 AM, Arnaud HERITIER wrote:
> Hi,
>
>
> For the API change I have also to open in issue at Atlassian
> http://jira.codehaus.org/browse/SWIZZLE-37
>
> I patched also testcases.
> There were issues w
Hi,
For the API change I have also to open in issue at Atlassian
http://jira.codehaus.org/browse/SWIZZLE-37
I patched also testcases.
There were issues with tests on dates (and some other things).
http://jira.codehaus.org/browse/SWIZZLE-38
Finally I fixed/improved the support to rea
Vincent, what's the snapshot needed for? R728944 is a change to maven 2.1's
parent no apparent reason this should affect the enforcer. Changing to a
snapshot for the site should technically block a release regardless if the
release plugin fails or not.
-Original Message-
From: vsive
It is slightly unnatural but unfortunately Hudson only launches the
slaves as a process, they don't run as persistent servers. However I
don't think it's completely useless because the testing and building
once maven runs is the same. We just have to fool with the env a bit
more.
The maven version
Vincent Siveton wrote:
Hi,
2008/11/7, ogusa...@apache.org :
Author: ogusakov
Date: Fri Nov 7 18:47:29 2008
New Revision: 712345
URL: http://svn.apache.org/viewvc?rev=712345&view=rev
Log:
added more helper types
Added:
maven/mercury/trunk/mercury-artifact/src/main/java/org/apa
On 24/12/2008, at 9:55 AM, Brett Porter wrote:
On 24/12/2008, at 4:22 AM, Paul Gier wrote:
I added a test case for MENFORCER-57. Maybe this can be included
in 1.0?
Yep, will take a look.
Fixed :)
Cheers,
Brett
I also noticed that the enforcer plugin is pointing to the 1-
SNAPS
On 24/12/2008, at 10:58 AM, Benjamin Bentmann wrote:
Now my question, how do we want to handle that smoothly on the grid?
I see three options:
a) Simply avoid using Maven 2.0.x for affected builds
b) Update the path translation in Maven 2.0.x to match 2.1.x
c) Update the *.bat files to ensur
Hi,
2008/11/7, ogusa...@apache.org :
> Author: ogusakov
> Date: Fri Nov 7 18:47:29 2008
> New Revision: 712345
>
> URL: http://svn.apache.org/viewvc?rev=712345&view=rev
> Log:
> added more helper types
>
> Added:
>
> maven/mercury/trunk/mercury-artifact/src/main/java/org/apache/maven/m
Hi,
today, the Hudson job for the Maven Release Plugin started failing [0].
In detail, the IT "invoker-basic" failed due to the Maven Release Plugin
getting configured with
mavenHome =
H:\home_hudson\.hudson\workspace\Maven-release-trunk\jdk\1.5\label\windows\trunk\maven-release-plugin\targe
On 24/12/2008, at 4:22 AM, Paul Gier wrote:
I added a test case for MENFORCER-57. Maybe this can be included in
1.0?
Yep, will take a look.
I also noticed that the enforcer plugin is pointing to the 1-
SNAPSHOT parent while the rules and api are pointing to the 2-
SNAPSHOT parent. So
On 24/12/2008, at 8:27 AM, Brian E. Fox wrote:
No one should be changing the RC branches unless it's a regression
fix and has been discussed.
I agree - the changes in POM v10 don't look significant enough to
warrant upgrading in the middle of a release, IMO.
Cheers,
Brett
--
Brett Port
We should try to include anything with patches and test cases for this
release. MENFORCER-55 can probably wait if a release is urgent. I might
have time to check it out later in the week but unlikely to get to it
before then.
I'll look at the commits later tonight and then we can decide the fate.
No one should be changing the RC branches unless it's a regression fix and has
been discussed.
-Original Message-
From: vsive...@apache.org [mailto:vsive...@apache.org]
Sent: Tuesday, December 23, 2008 10:23 AM
To: comm...@maven.apache.org
Subject: svn commit: r728996 -
/maven/component
I added a test case for MENFORCER-57. Maybe this can be included in 1.0?
I also noticed that the enforcer plugin is pointing to the 1-SNAPSHOT parent
while the rules and api are pointing to the 2-SNAPSHOT parent. So I had trouble
building locally without the snapshot repository in my settings
De Smet Ringo wrote:
What is the best way for a plugin to spawn Maven again in a subprocess?
http://maven.apache.org/shared/maven-invoker/
If there is any existing code, can you give me a pointer to it, or provide me
with an example?
http://maven.apache.org/plugins/maven-invoker-plugin/
h
have a look at maven-invoker which is used by the maven-invoker-plugin
2008/12/23 De Smet Ringo
> Hello,
>
> We have a custom plugin that, for some functionality, spawns Maven again
> but with other arguments. The current implementation depends on the
> MavenExecutor from the maven-release-plugi
Hello,
We have a custom plugin that, for some functionality, spawns Maven again but
with other arguments. The current implementation depends on the MavenExecutor
from the maven-release-plugin:2.0-beta-4. I updated the dependency to
2.0-beta-8, but in there, the API to MavenExecutor has changed
On 23-Dec-08, at 9:34 AM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
I think this is a regression:
http://jira.codehaus.org/browse/MNG-3922
Attached artifacts with classifiers seem to have gotten hosed.
Works in 2.0.8. No worky in 2.0.9.
I don't get that working with Maven 2.0.8 either
Hi,
I went through and closed out most of the issues in JIRA relevant for
1.0 of the enforcer and added some more unit tests. All that is left
is the documentation which I was going to give a quick look at tomorrow.
Are there are any other things that someone needs to be addressed
before
Jason van Zyl wrote:
I think this is a regression:
http://jira.codehaus.org/browse/MNG-3922
Attached artifacts with classifiers seem to have gotten hosed. Works in
2.0.8. No worky in 2.0.9.
I don't get that working with Maven 2.0.8 either, i.e. I don't believe
it's a regression, so could b
20 matches
Mail list logo