Benjamin Bentmann wrote:
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0.1 before the actual release of 3.0.2.
Works
In 6245a072-ee21-4b6a-87cf-1ce84ea4e...@apache.org Brett Porter wrote:
http://jira.codehaus.org/browse/SCM-581
It isn't clear from the issue whether this is in the SCM provider (which is
independent of Maven releases), or in Maven (in which case this is filed in
the wrong place).
Right.
Brett Porter wrote:
http://jira.codehaus.org/browse/SCM-581
It isn't clear from the issue whether this is in the SCM provider
(which is independent of Maven releases), or in Maven (in which case
this is filed in the wrong place).
I think I've actually tracked it down now, to the
So... about the double slashes issue SCM-581...
I've opened a MNG-issue that contains a simplistic patch and a fix for the
relevant test case too. The fix might be a bit invasive as it affects all
url:s, not only the scm connection url. The alternative is perhaps to have a
separate UrlNormalizer
Hello,
I understand if this is strictly not a concern or blocker for a release of
maven itself, but SCM-581 is still blocking a upgrade from 2.2.1 to 3.x
including 3.0.2-RC1 for anyone using mercurial (hg) as SCM and absolute paths
on a remote server with the maven release plugin.
Fredrik Jonson wrote:
Any chance to get a fix for that included in 3.0.2?
Unlikely.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
It isn't clear from the issue whether this is in the SCM provider (which is
independent of Maven releases), or in Maven (in which case this is filed in the
wrong place). What is the difference in behaviour between Maven 2.2.1 and Maven
3.0? Is there a relevant MNG issue for that?
On
Works for me building JBoss AS and some other projects.
On 01/05/2011 03:20 PM, Benjamin Bentmann wrote:
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential
Hi,
I test m3 3.0.2-RC1 and maybe it's regression :
[WARNING] The metadata
/Users/carpentierxqvier/.m2/repository/com/greenivory/redmole/client/commons/com.greenivory.redmole.client.commons/2.3.0-SNAPSHOT/maven-metadata-local.xml
is invalid: Snapshot information corrupted with remote
No problem with my tests.
Arnaud
On Wed, Jan 5, 2011 at 10:20 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and following
tradition we invite interested users in taking the RC for a test drive in
order to detect and
I'm having a problem with the release plugin, BOMs in the reactor, and
Maven 3.x. I just uncovered the problem last night, and spent a good
part of today trying to narrow it down and verify that it isn't
something I'm doing wrong.
The issue is http://jira.codehaus.org/browse/MNG-4962
This
I should mention that this is a problem I have verified is still present
in 3.0.2-RC1, but it's also happening in all the 3.x releases.
Maven 2.2.1 works fine.
On 1/6/11 5:30 PM, John Casey wrote:
I'm having a problem with the release plugin, BOMs in the reactor, and
Maven 3.x. I just
Hi,
Works fine for all Sonar projects, including builds with Tycho.
On Fri, Jan 7, 2011 at 01:32, John Casey jdca...@commonjava.org wrote:
I should mention that this is a problem I have verified is still present in
3.0.2-RC1, but it's also happening in all the 3.x releases.
Maven 2.2.1
Hi,
may be i have observed a little issue...
I have checked the following project
https://github.com/khmarbaise/Maven-Licenses-Verifier-Plugin
and did an
mvn clean package
on it.
The result was that twice times the line
Running TestSuite
occured with with MVN 3.0.2-RC1 but not not with
Karl Heinz Marbaise wrote:
I have observed that behaviour with maven-surefire 2.7.1 (in
relationship with Maven 3.0.1) but i use maven-surefire plugin
2.4.3...(see http://jira.codehaus.org/browse/SUREFIRE-680)
From your build's log:
[INFO] --- maven-surefire-plugin:2.7.1:test (default-test)
Hi,
outch...i've found the problem...as i expected it was my pom which was
the problem...not the release...
Sorry for that noise...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#:
Hi Benjamin,
which matches the observation that your POM locks down
maven-surefire-report-plugin to 2.4.3 but not maven-surefire-plugin.
Yes you're right...Mea culpa...
Fixed that in my project...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405
Works for me for building and working with
- Maven Android Plugin
- Maven Android SDK Deplouer
- a JasperServer war project
- ksaop2-android project
- Maven Android Plugin Samples project (4 android project including a
scala one)
manfred
http://www.simpligility.com
Hi,
we're aiming at a
18 matches
Mail list logo
