Assuming that filters could be set for the compile and testCompile goals, passing them as parameters to the mojo would work just fine. I'll update the ticket and add a patch later today.
Thanks btw. This one is very important to me, as much so as the xml beans plugin was. Kris > [ http://jira.codehaus.org/browse/MNG-643?page=all ] > > Brett Porter updated MNG-643: > ----------------------------- > > Priority: Major (was: Blocker) > Fix Version: 2.0-beta-2 > Component: (was: maven-model) > maven-plugins > > I'm all for including this, but let's just expose it as parameters of the > compiler mojo. Reasons: > > 1) that's fine, but it's not project metadata > 2) that's bad, we should not support it in the metadata. For example, it > won't map to an IDEA project > 3) belongs in that particular plugin's configuration, its not project > metadata > 4, 5) I don't understand your points on these ones, sorry > > I'm -1 to the pom format mentioned above: > - would rather not introduce metadata for something that doesn't describe > the project, instead going to plugin configuration > - I don't consider this backwards compatible - we don't want to keep both > as its confusing, which means deprecating the first, which means removing > it before the final 2.0 release. I wouldn't be particularly happy with > that. > > I hope this is reasonable? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
