On 04/09/2007, at 7:40 PM, Jörg Schaible wrote:
Brett Porter wrote on Tuesday, September 04, 2007 10:31 AM:
On 04/09/2007, at 6:24 PM, Jörg Schaible wrote:
- calling a goal that does not need a POM in the current dir in a
multi-project root Examples:
mvn install:install-file <args>
mvn archetype:create <args>
Maven walks down the complete project hierarchy ...
But Maven can't tell the difference between "doesn't need a
POM" (archetype, which can use it and add a <module> if it exists)
and "shouldn't use a POM" (install-file), so this isn't an error
condition. It's something the plugin developers need to take into
account.
Yes, but has the Mojo any chance of telling this to Maven? I am not
too familiar with the internals, but I assume that the evaluation
of the POMs takes place before the goal is called. If the Mojo has
already the possibility to supress the traversal of the modules,
then I agree and it's a simple bug in the goal.
That's one of the things @aggregator is used for (though it has had
problems as Brian showed). Anyway, I was just pointing out it wasn't
related to the discussion at hand :)
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
