[
https://issues.jboss.org/browse/JBIDE-19688?page=com.atlassian.jira.plugi...
]
Sylvain Paillé updated JBIDE-19688:
-----------------------------------
Steps to Reproduce:
Enable Workspace Resolution in Eclipse
Make 2 projects A and B.
B has a dependency to A.
Project B is a deployable WAR.
Run Project B to Wildfly.
Watch deployed jar into WEB-LIB/lib.
You can observe there is a directory named "project-a.jar" instead of jar file.
Disabling Workspace resolution will prevent jar exploding into directory.
was:
Enable Workspace Resolution in Eclipse
Make 2 projects A and B.
B has a dependency to A.
Project B is a deployable WAR.
Run Project B to Wildfly.
Watch deployed jar into WEB-LIB/lib.
You can observe there is a directory with the B project name.
"project-b.jar" is a directory.
Disabling Workspace resolution will prevent jar exploding into directory.
Eclipse m2e, workspace resolution and Wildfly deployment issues
---------------------------------------------------------------
Key: JBIDE-19688
URL:
https://issues.jboss.org/browse/JBIDE-19688
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Sylvain Paillé
Hello !
I just found on Wildfly a Jboss (resolved ?) related bug.
See :
https://issues.jboss.org/browse/AS7-4704
When using Eclipse and m2e plugin, deploy with "workspace resolution" make
WEB-INF/lib/ jar to be exploded into directories ...
Wildfly simply ignore them when running app.
Disabling Workspace resolution is a workaround.
Have you met a similar bug ?
Thx
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)