+1, please cut beta-5
On 4/19/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
I agree. Why not release beta-5 now and then 6 when your changes are
ready?
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:14 AM
To: Maven Developers List
Su
I checked my local repo and I have maven-release 1-SNAPSHOT, so I didn't
encounter the first problem that you had earlier. I removed 1-SNAPSHOT
from my repo, and was able to duplicate your first error, so I changed
the version to 1. Then I tried building maven-release again and was able
to buil
Issue Subscription
Filter: Design & Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
Hello,
I did a checkout of maven-release from the trunk, then I did a mvn clean
followed by a mvn install.
That failed because maven-release-plugin ver 1-SNAPSHOT does not exist at
http://repo1.maven.org/maven2.
So I changed the version from 1-SNAPSHOT to 1.
That did build but now the tests fail s
Hmm.. it builds successfully in my machine.
Try to update your source and build again :)
-Deng
Pankaj Tandon wrote:
Hi there,
I changed the version from 1-SNAPSHOT to 1 which exists on repo1.
That fixed the download but now all the tests fail.
Here is the output:
Thanks,
Pankaj
...
[INFO] [sur
Hi there,
I changed the version from 1-SNAPSHOT to 1 which exists on repo1.
That fixed the download but now all the tests fail.
Here is the output:
Thanks,
Pankaj
...
[INFO] [surefire:test]
[INFO] Surefire report directory:
D:\projects\maven-release\maven-release-manage
r\target\surefire-reports
Hi,
I checked out the following code from http://svn.apache.org/repos/asf
All the projects under maven-components from the trunk
mavent-release-manager and maven-release-plugin from maven/release/trunk
into maven-release folder.
I then did a mvn install from the maven-release folder.
When I do th
I agree. Why not release beta-5 now and then 6 when your changes are ready?
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:14 AM
To: Maven Developers List
Subject: Re: Release the maven-release-plugin?
I think it makes sense to releas
I think it makes sense to release a beta-5 if the changes are major
enough. There's nothing that prevents you from releasing beta-6 or
-rc1 afterwards.
Robert, I'll have a look to the issues now.
Thanks,
Stéphane
On 4/19/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I'd like to add more feat
I'd like to add more features in this plugin before to release it like branch
creation, check SNAPSHOTS in properties and not used in dependencies versions
For the moment, the release is planned to be done in one month, after the
release of Maven-SCM 1.0 final.
Emmanuel
Robert Kopco a écrit :
Thank you very much!
Now there are 19 of 25 issues fixed. In would be very happy if the current
state could be released as 2.0-beta-5. The rest should be moved to the next
version. Besides MRELEASE-6 (which has been open for 1 1/2 years) none of
the remaining issues is critical.
What do you
>If you know well the perforce command line, maybe you can help Mike on the
Maven SCM Perforce provider because he
>doesn't use Continuum so he don't know pb with Perforce/Continuum and can't
fix them.
currently I use (built from svn - jdk 1.5) continuum & archiva deployed in
tomcat 6
several th
On 4/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I posted this issue some weeks ago. Now I verified that this issue still
exists in Maven 2.0.6.
Maybe someone can help with JIRA MNG-2784?
Last time you mentioned it, Jason asked for tests.
--
Wendy
---
>System.clearProperty doesn't exist in jdk 1.4
don't realize it ...
> Perforce isn't well supported in continuum due to a Maven-SCM issue in
> the perforce provider (http://jira.codehaus.org/browse/SCM-292)
> When this issue will be fixed, Continuum will work well with Perforce.
jira should be i
Hi,
I posted this issue some weeks ago. Now I verified that this issue still
exists in Maven 2.0.6.
Maybe someone can help with JIRA MNG-2784?
Thanks in advance,
Maik
15 matches
Mail list logo