I have done something to get the clean to work from the top-level. Just don't know what it was.
Next problem will probably be related though. When trying to do a build from the top-level it goes fine until after it processes a subproject with other subprojects in it. After finishing the first set of sub-subprojects it chokes when trying to process the next subproject at the top level. It fails with a similar "Unable to obtain goal [build] -- file:/C:/dev/newcvs/dbselection/:11:41: <attainGoal> No goal [jar:install]". ([build] is my defined goal in each project).
I added "maven.multiproject.excludes=project.xml" to the project.properties file of the subproject with subprojects and it has no effect.
What am I missing? Brent
Rafal Krzewski wrote:
[EMAIL PROTECTED] wrote:
You've got the top level project included in the set of directories that multiproject is processing.
This is not supported ATM.
My guess is that is caused by a bug in Werkz, or in the way Maven uses them. When you try to run goals on a project for the second time in a maven run it complains about them being undefined, instead of just skipping them silently (because they are done).
For the time being, the multiproject plugin might be improved by extracting the bit that iterates over projects and checks for a duplicaing top level project in sub project into a reusable tag (it also sets the 'reactorProjects' variable).
I'll take a look at this later.
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
