I made a change to the scm project to fix a bug that was bugging me. Built the 1.3-SNAPSHOT version of the latest SCM plugin, tested it, and it works fine.
Now I want to do a formal release of my own personalized version of the project. The release:prepare fails because of missing dependencies between modules. The only solution I know of is to add the install goal to the preperationGoals configuration. But I am sure Oliver didn't have to do this when he cut the latest release of this project not too long ago (or maybe he did ;-)). I just don't know what it is about the release plugin which causes it to fail. Individuals on this list have made clear claims that you should NOT have to do an install when you have module dependencies. Any thoughts or discussion here would be very much appreciated. The build fails on the maven-scm-plugin project (which is a module of the scm project itself. Here is a snippet. [INFO] [INFO] ------------------------------------------------------------------ ------ [INFO] [ERROR] BUILD ERROR [INFO] [INFO] ------------------------------------------------------------------ ------ [INFO] [INFO] Failed to resolve artifact. [INFO] [INFO] Missing: [INFO] ---------- [INFO] 1) org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nortel-1 [INFO] Path to dependency: [INFO] 1) org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-no rtel-1 [INFO] 2) org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nor tel-1 [INFO] [INFO] ---------- [INFO] 1 required artifact is missing. [INFO] [INFO] for artifact: [INFO] org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-nortel-1 [INFO] [INFO] from the specified remote repositories: [INFO] nexus (http://nexus.norforge.nortel.com/content/groups/public) --- Todd Thiessen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
