Thanks John. I will try next RC and comment in Jira issue if there is still a problem.
----- Message d'origine ---- De : John Casey <[EMAIL PROTECTED]> À : Maven Developers List <dev@maven.apache.org> Envoyé le : Vendredi, 18 Juillet 2008, 17h18mn 53s Objet : Re: Re : [PLEASE TEST] Maven 2.0.10-RC1 Okay, I've duplicated the problem, and generated a simple test case to replicate it separately from the JWebUnit project, so we can create an integration test. The JIRA issue is: http://jira.codehaus.org/browse/MNG-3671 I have a fix for this issue (I believe), but still need to formalize the attached test POM into an integration test before closing this issue. -john John Casey wrote: > I'll give it a try today and see if I can reproduce the problem. Then, > we should file a JIRA ticket so it shows up on the release notes, and > I'll fix it. > > Thanks for testing! > > -john > > Julien HENRY wrote: >> Hi John, >> >> I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my >> module is depending on the other one using this syntax: >> <dependency> >> <groupId>net.sourceforge.jwebunit</groupId> >> >> <artifactId>jwebunit-webtestcase-generator</artifactId> >> <version>${pom.version}</version> >> </dependency> >> >> And Maven try to download: >> >> [INFO] Building Core - API >> [INFO] task-segment: [clean, install] >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] [clean:clean] >> [INFO] Deleting directory D:\Perso\jwebunit\jwebunit-core\target >> [INFO] Preparing exec:java >> [WARNING] Removing: java from forked lifecycle, to prevent recursive >> invocation. >> [INFO] No goals needed for project - skipping >> Downloading: >> http://repository.codehaus.org/net/sourceforge/jwebunit/jwebunit-webtestcase-generator/${pom.version}/jwebunit-webtestcase-generator-${pom.version}.pom >> >> >> org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate >> resource in repository >> >> I tried to change it to ${project.version} and it doesn't work also. >> >> If you want to try just checkout >> https://jwebunit.svn.sourceforge.net/svnroot/jwebunit/trunk >> >> Regards, >> >> Julien >> >> >> >> ----- Message d'origine ---- >> De : John Casey <[EMAIL PROTECTED]> >> À : Maven Developers List <dev@maven.apache.org> >> Envoyé le : Mercredi, 16 Juillet 2008, 0h23mn 46s >> Objet : [PLEASE TEST] Maven 2.0.10-RC1 >> >> 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/ >> >> >> >> 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] _____________________________________________________________________________ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
