You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Neale (JIRA)" <ji...@codehaus.org> on 2009/06/22 16:06:15 UTC

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

    [ http://jira.codehaus.org/browse/MECLIPSE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181115#action_181115 ] 

Neale commented on MECLIPSE-560:
--------------------------------

This is an issue affecting a large number of use cases, as the WTP tooling always prefixes the path with a /

An example use case that is annoying me, and causing WARs to not deploy is that after "mvn eclipse:eclipse", I have:
{code}
        <wb-resource deploy-path="/" source-path="src/main/java"/>
        <wb-resource deploy-path="/" source-path="src/main/resources"/>
{code}

And if I then apply an exclusing pattern to the src folder under "Configure Build Path..." the file is modified to:

{code}
        <wb-resource deploy-path="/" source-path="src/main/java"/>
        <wb-resource deploy-path="/" source-path="src/main/resources"/>
        <wb-resource deploy-path="/" source-path="/src/main/java"/>
{code}

While I don't necessarily agree with the WTP team's approach, I do think that the plugin should fit with what they do, and save us all the hell that otherwise follows.


> EAR file WTP config generation Incompatible with RAD7
> -----------------------------------------------------
>
>                 Key: MECLIPSE-560
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-560
>             Project: Maven 2.x 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 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