"Project references" - I assume you mean project.getArtifact() ? This can only happen when the artifact is created (or a semblance of it) - ie at compile, package, install phases where it is target/classes, target/XXX.jar or the local repository versions respectively.
- Brett John Casey (JIRA) wrote: > [ http://jira.codehaus.org/browse/MNG-1766?page=comments#action_52916 ] > > John Casey commented on MNG-1766: > --------------------------------- > > appears that the project references aren't being resolved correctly. I'll > have to attach a debugger and figure out why. > > UPDATE: To duplicate this problem, you actually need to: > > 1. Remove all traces of org/apache/maven/it2002/* from your local repo > 2. Comment out the line: 'mvn clean install' in it2002/test.sh > 3. Run test.sh in it2002 dir. > >> release:prepare should not require multimodule artifacts to be in the local >> repository >> -------------------------------------------------------------------------------------- >> >> Key: MNG-1766 >> URL: http://jira.codehaus.org/browse/MNG-1766 >> Project: Maven 2 >> Type: Bug >> Components: maven-release-plugin >> Versions: 2.0.1 >> Reporter: John Casey >> Assignee: John Casey >> Fix For: 2.0.2 > >> >> Currently, if you try to run release:prepare on a multimodule project after >> removing any of that build's artifacts from the local repository, it will >> fail. Investigate why release:prepare needs the multimodule artifacts >> installed in the local repository before it can succeed. >> To reproduce, comment the following line in it2002/test.sh: >> mvn clean install >> NOTE: This may have to do with the version resolution code, which is used to >> resolve SNAPSHOT versions. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
