[
https://jira.jboss.org/browse/JBIDE-6596?page=com.atlassian.jira.plugin.s...
]
Bernhard Hurzeler commented on JBIDE-6596:
------------------------------------------
Yes certainly. Try to create a seam/maven project and you will find a very similar issue
as was reported by Dominik. First the jboss-seam.jar is put in a folder and secondly maven
libraries that are marked as packaging jar or ejb gets put in a jar file of the same name
i.e. some.jar is jared in a file called some.jar. Hence as a consequence the classes
can't be found and the war is not working properly. I suspect that this is the same
issue as Dominik reported.
New Seam WAR project has incorrect deployment artifact structure
----------------------------------------------------------------
Key: JBIDE-6596
URL:
https://jira.jboss.org/browse/JBIDE-6596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.M1
Environment: JBT 3.2.0.M1
EAP 5.0, EAP 5.1.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.M1
New Seam Project wizard creates project with incorrect structure, deployment of the
project fails.
The deployed artifact contains:
/WEB-INF/lib/jboss-seam.jar/jboss-seam.jar
instead of:
/WEB-INF/lib/jboss-seam.jar
Steps to reproduce:
1) Register and start EAP 5.0 runtime
2) File -> New -> Seam Web project, choose EAP 5.0 runtime and EAP 5.0 Seam, WAR
packaging option
3) Wait until project gets deployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira