[
https://issues.apache.org/jira/browse/MECLIPSE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-304.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Removing @execute phase="generate-resources"
> --------------------------------------------
>
> Key: MECLIPSE-304
> URL: https://issues.apache.org/jira/browse/MECLIPSE-304
> Project: Maven Eclipse Plugin
> Issue Type: Improvement
> Components: M2Eclipse support
> Affects Versions: 2.4
> Environment: Windows 2003
> Reporter: Auston McReynolds
> Priority: Minor
>
> eclipse:m2eclipse and eclipse:eclipse shouldn't have to @execute
> phase="generate-resources".
> By removing this line and adding @phase generate-resources I can now run
> eclipse:eclipse at the parent POM level as well as at the module level, with
> ONE CATCH:
> In org.apache.maven.plugin.eclipse.EclipsePlugin theres a TODO:
> // TODO: Why are we using project in some places, and executedProject in
> others??
> Well, once you remove the @execute you receive a barrage of NPE's.
> However if within org.apache.maven.plugin.eclipse.EclipsePlugin @ validate()
> I add
> executedProject = this.project; to the top, everything works like a charm.
> Can a configuration or flag be added that allows no @execution with the above
> modification?
> Regards,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
