Hang on a second though; since we're attempting to release 2.0.10, why
not file the issues under there?
I think I'd rather see that happen, since then the final release notes
for 2.0.10 will incorporate any issues we find along the way.
-john
Jason van Zyl wrote:
John, maybe a new version in JIRA to help track issues/regressions for
the RC cycle would help. Brian ended up doing 9 RCs so I'm sure we'll
get close to that again. Especially given what look like fundament
problems with wagon/artifact resolution.
On 16-Jul-08, at 8:12 AM, nicolas de loof wrote:
Running mvn eclipse:eclipse on my project dump many stacktrace on the
console :
Downloading:
http://sai1rennes:8888/archiva/repository/releases/org/jmock/jmock/2.4.0/jmock-2.4.0-javadoc.jar
org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate
resource in repository
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:132)
...
The requested artifact is not present in the repo, but this is not
blocker
and maven 2.0.9 does not dump such errors.
2008/7/16 John Casey <[EMAIL PROTECTED]>:
Hi again,
As promised, I've staged the first release candidate for Maven 2.0.10
here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
The issues resolved for this release (so far) are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
still open. This is because one of the possible solutions to this
issue -
and the only one that the Maven project really has control over -
depends on
re-releasing a new version of commons-build-plugin that will depend
on the
eventual 2.0.10 version of maven-script-ant.
Please, try out this release candidate and let me know what's broken!
Once
things stabilize, I'll kick it out to the users to have a go, then if
it's
still stable after that (or, whatever RC we find is stable at that
point),
I'll call a vote to release. At that point, I'll run a new build to
generate
artifacts without the RC# suffix in the version.
Thanks!
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
