[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156014#action_156014
]
Benjamin Bentmann commented on MECLIPSE-414:
--------------------------------------------
bq. I'm looking into why it needs a forked lifecycle...
For goals that are primarily run from the CLI, there is not other way to tell
about generated sources/resources. I.e. without forking a build up to
"generates-resources", the plugin would only see the static source/directories
specified in the POM and would miss stuff that gets dynamically generated.
> 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
