We are using the maven-multiproject-plugin-1.1 with maven 1.0RC1 to iterate through projects
and attain goals (clean, install, deploy, site, etc...). We use ClearCase as or SCM.
We are having a problem with the multiproject:clean goal. This goal simply uses the reactor
to iterate through subprojects and run the clean:clean goal. The clean:clean goal deletes
the ${maven.build.dir}. All works well until we introduce a new subproject. The first time
the hourly cruisecontrol build runs it will invoke multiproject:clean and fail because maven
is unable to resolve dependency on new subproject/artifact. This is a chicken-and-egg
scenario as the artifact does not exist because it has not yet been built and installed or
deploy to maven repository. See error message below.
I considered ignoring the multiproject:clean failures using the multiproject.ignoreFailures
property. This will result in target directories being left behind.
I also considered implementing clean in maven.xml as the apache geronimo project does.
However, I would prefer not to bypass the clean plugin as the implementation of clean
goal may change in future versions.
Does anyone in the maven user community have a recommendation (best practise)
for dealing with this problem?
** MAVEN ERROR MESSAGE **
cmd> maven clean:clean
Attempting to download datasource-workflow-impl-1.0.jar. WARNING: Failed to download datasource-workflow-impl-1.0.jar. The build cannot continue because of the following unsatisfied dependency:
datasource-workflow-impl-1.0.jar (no download url specified)
Total time: 4 seconds Finished at: Thu May 20 13:22:36 EDT 2004
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
