I'm closing in on the problem, and found the way to make it work/break. Though I'm completely lost on which project to file the bug against even...
The parent mule-tools project had several more maven plugins. Once I removed all of them and left MAV only, it detected the extractor. I'm attaching 2 debug runs, one for the direct invocation from the folder and the invalid one for the parent with other plugins. http://www.nabble.com/file/8476/debug_logs_2_runs.zip debug_logs_2_runs.zip The org.apache.maven.tools.plugin.scanner.DefaultMojoScanner gets injected with 2 extractor names only, couldn't trace it further. Any advice on the direction (which plugin has the bug) is much appreciated. -- View this message in context: http://www.nabble.com/-groovy-user--Let-your-Mojo%27s-be-Groovy-baby%21-tf3529339s177.html#a10654732 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
