[ http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barrie Treloar closed MECLIPSE-414. ----------------------------------- Resolution: Not A Bug As per Benjamin Bentmann's comments; the eclipse plugin being run from the CLI will never have access to other plugins unless run via @execute. Therefore can't removed executedProject as this is the result of the forked lifecycle which contains the information we want. Marking as not a bug. > Not beeing @aggregator, eclipse plugin does not require executedProject > ----------------------------------------------------------------------- > > Key: MECLIPSE-414 > URL: http://jira.codehaus.org/browse/MECLIPSE-414 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Affects Versions: 2.5 > Reporter: nicolas de loof > Assignee: Barrie Treloar > Fix For: 2.6 > > > The eclispe plugin uses both ${executedProject} and ${project}. > Not beeing an aggregator plugin, ${project} is allways tghe currently > executed project, and the projectDirectory is project.getBasedir(). > Having two attributes for same target makes the plugin harder to understand -- 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