[ http://jira.codehaus.org/browse/MNG-392?page=comments#action_39038 ] Brett Porter commented on MNG-392: ----------------------------------
Jason, there is an open bug to flag a mojo as "requiring a project" to work in the mojo descriptor instead of this - do you think that is a better alternative than changing base classes? This could also then require a project, without actually having to take a project as a field - keeping it separated from Maven, but allowing Maven to handle it smartly. I'd actually think that the Eclipse and IDEA plugins should be able to take a Model, not a MavenProject so that they could work with a POM-like structure from Ant. The barrier to this is the use of resolved artifacts instead of the dependencies list, so if they were passed in separately and the Ant tasks were used to resolve them, there shouldn't really be a need for a project at all. > Make an abstract mojo that works with MavenProject > -------------------------------------------------- > > Key: MNG-392 > URL: http://jira.codehaus.org/browse/MNG-392 > Project: m2 > Type: Task > Versions: 2.0-alpha-3 > Reporter: Jason van Zyl > Fix For: 2.0-alpha-3 > > > For mojos like eclipse:eclipse and idea:idea it would be nice to have an > abstract mojo that can have common code for validation. Like checking for the > existence of a project. Any of the IDEA mojos would be candidates for use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
