Bug 967549
| Summary: | Seam2.3 projects generated by seam-gen contains doubled jboss-deployment-structure xml | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Tomas Remes <tremes> |
| Component: | Seam | Assignee: | Marek Novotny <mnovotny> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas Remes <tremes> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | snagarwa |
| Target Milestone: | CR1 | ||
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Seam-gen generated applications of type EAR had duplicated jboss-deployment-structure.xml file in <EAR>/META-INF/ and <WAR>/WEB-INF directories. This has been fixed by removing the duplication from EAR type projects.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-16 11:34:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tomas Remes
2013-05-27 12:22:12 UTC
To be clear - it looks like that the reason of the error is other problem. Anyway I think there should be only one jboss-deployment-structure descriptor. Tomas, could you create an upstream jira issue for this? added exclusion for war target in EAR type project. Fixed by https://source.jboss.org/changelog/Seam?cs=15547 This fix is not correct. I can still see this file in META-INF and WEB-INF in WAR project as well as in EAR project. I think this should be fixed in jboss-seam-gen/build.xml file (just add exclusion into file-copy target) instead of jboss-seam-gen/build-scripts/build.xml file. I meant these files in generated project, where this could be little bit misleading, and not the files in created deployment. Sorry for confusion. In the deployment is it ok. Verified in 2.3.0.CR1 release. Updated doc text. Note: This bug was not a known issue in wfk 2.2 RN. |