[ http://jira.codehaus.org/browse/MNGECLIPSE-31?page=comments#action_55639 ]
Eugene Kuleshov commented on MNGECLIPSE-31: ------------------------------------------- I am not convinced that it should be actually exposed to the end user. irst of all plugin also require a special nature and we can guarantee that all of that won't change in the future (neither Eclipse platform guarantee that). It is also unclear why one would need to use eclipse:eclipse goal if this plugin is installed in Eclipse and allows to handle this enablement easily. I would like to hear some practical use case. Basically our goal is to eliminate any need for generating Eclipse project files from the command line. > eclipse:eclipse goal can switch enabled on and off using "buildcommands" - > Add to documentation > ----------------------------------------------------------------------------------------------- > > Key: MNGECLIPSE-31 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-31 > Project: Maven 2.x Plug-in for Eclipse > Type: New Feature > Reporter: David Boden > Assignee: Eugene Kuleshov > Priority: Trivial > > > This is just a documentation issue. > Please advise the user that you can create a buildcommands section of pom.xml > to add: > <buildCommand> > <name>org.maven.ide.eclipse.maven2Builder</name> > <arguments> > </arguments> > </buildCommand> > This results in your plugin being set to "enable". > Related to http://jira.codehaus.org/browse/MECLIPSE-54 -- 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]
