[jbosstools-issues] [JBoss JIRA] (JBIDE-12369) Deployment of maven project via JBDS doesn't use proper deployment information

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707766#comment-12707766 ] 

Fred Bricon commented on JBIDE-12369:
-------------------------------------

You need to remove the <earSourceExcludes>**/application.xml</earSourceExcludes> from your ear plugin config. And update the ear project configuration (right click on project > Maven > Update project configuration.

Basically all exclusion patterns in the pom are translated to packaging exclusion patterns in WTP / the JBoss AS server adapter. There's no easy way to match that maven feature in WTP, so it's a trade-off and you've hit one of the corner cases.

You should also remove one of the 2 maven-ear-plugin versions in your pom, but that's unrelated.

                
> Deployment of maven project via JBDS doesn't use proper deployment information
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-12369
>                 URL: https://issues.jboss.org/browse/JBIDE-12369
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: maven
>         Environment: RHEL 6.2
> JBDS 5.0.0.GA
> Maven 3.0.3
>            Reporter: Tomas Repel
>            Assignee: Fred Bricon
>         Attachments: deploy-example.tar.gz
>
>
> If maven project (packaged as ear) is deployed via JBDS (using m2e), the proper deployment information is not generated. This causes the URL of the project is different from the URL when ear file is created and deployed via maven directly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira