[jira] (MECLIPSE-560) EAR file WTP config generation Incompatible with RAD7

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MECLIPSE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MECLIPSE-560.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> EAR file WTP config generation Incompatible with RAD7
> -----------------------------------------------------
>
>                 Key: MECLIPSE-560
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-560
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: WTP support
>    Affects Versions: 2.6
>            Reporter: Rustam Abdullaev
>
> It seems like for *.ear* modules that keep META-INF in the _root of the project_ (the "IBM RAD way") i.e.
> {code:xml} <!-- in the maven-ear-plugin config -->
> <earSourceDirectory>${basedir}</earSourceDirectory>{code}
> the file *.settings/org.eclipse.wst.common.component* is not generated correctly, specifically the following line is incorrect:
> {code:xml}<wb-resource deploy-path="/" source-path="."/>{code}
> It should be:
> {code:xml}<wb-resource deploy-path="/" source-path="/"/>{code}
> This bug results in a complete break down of RAD 7 J2EE functionality (it can no longer recognize WTP modules, edit J2EE dependencies or open Manifest.mf files). Regular Eclipse WTP may also be affected, but was not tested.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)