[
http://jira.codehaus.org/browse/MECLIPSE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MECLIPSE-279.
-----------------------------------
Resolution: Fixed
> PDE projects should be considered java projects in all cases
> ------------------------------------------------------------
>
> Key: MECLIPSE-279
> URL: http://jira.codehaus.org/browse/MECLIPSE-279
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.4
> Environment: java version "1.5.0_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
> Reporter: Graham Leggett
> Fix For: 2.4
>
> Attachments: pde-fix.diff
>
>
> When an attempt is made to use the pde-maven-plugin to build plugin code,
> this attempt fails.
> It turns out that when the PDE artifact is set to zip as required by the
> pde-maven-plugin, it in effect tells the maven-eclipse-plugin that this
> artifact is no longer a java artifact.
> The effect is that the .classpath file is not written, and this breaks the
> eclipse build.
> The fix is to modify the isJavaProject test to treat all PDE projects as java
> projects, regardless of the packaging type.
> The attached patch allows the pde-maven-plugin and maven-eclipse-plugin to
> work together again.
--
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
