[
https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12369:
----------------------------------------
Summary: Deployment of maven project which uses excludeSource doesn't work the
same as maven cli (was: Deployment of maven project via JBDS doesn't use proper
deployment information)
updated the title to reflect the core problem.
As Fred says, this is one of the cornercases that cannot be directly translated from Maven
to WTP.
We will look at adding a warning since we can detect this possible problem.
Deployment of maven project which uses excludeSource doesn't work
the same as maven cli
---------------------------------------------------------------------------------------
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