[JBoss JIRA] (JBIDE-12369) Deployment of maven project via JBDS doesn't use proper deployment information
1:18 p.m.
Tomas Repel created JBIDE-12369:
-----------------------------------
Summary: 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
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
1:24 p.m.
[
https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugi...
]
Tomas Repel updated JBIDE-12369:
--------------------------------
Attachment: deploy-example.tar.gz
Use the example from attachment to reproduce the behaviour. In case of JBDS deployment,
the URL is http://localhost:8080/deploy-example-web.
In case of maven deployment the URL is http://localhost:8080/deploy-example-contextroot
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
2:12 p.m.
[
https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugi...
]
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
9:42 a.m.
New subject: [JBoss JIRA] (JBIDE-12369) Deployment of maven project which uses excludeSource doesn't work the same as maven cli
[
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
10:02 a.m.
New subject: [JBoss JIRA] (JBIDE-12369) Deployment of maven project which uses excludeSource doesn't work the same as maven cli
[
https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-12369:
--------------------------------
Component/s: UpStream
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, UpStream
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:09 p.m.
New subject: [JBoss JIRA] (JBIDE-12369) Deployment of maven project which uses excludeSource doesn't work the same as maven cli
[
https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12369:
---------------------------------------------
upstream cornercase - lets look at options at f2f2012
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, UpStream
Environment: RHEL 6.2
JBDS 5.0.0.GA
Maven 3.0.3
Reporter: Tomas Repel
Assignee: Fred Bricon
Labels: f2f2012
Fix For: 4.1.x
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:09 p.m.
New subject: [JBoss JIRA] (JBIDE-12369) Deployment of maven project which uses excludeSource doesn't work the same as maven cli
[
https://issues.jboss.org/browse/JBIDE-12369?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12369:
----------------------------------------
Fix Version/s: 4.1.x
Labels: f2f2012 (was: )
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, UpStream
Environment: RHEL 6.2
JBDS 5.0.0.GA
Maven 3.0.3
Reporter: Tomas Repel
Assignee: Fred Bricon
Labels: f2f2012
Fix For: 4.1.x
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4234
days inactive
4354
days old
jbosstools-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Fred Bricon (JIRA) -
Max Rydahl Andersen (JIRA)
-
Tomas Repel (JIRA)