Bug 1000094
| Summary: | Add maven components to tomcat6,7 | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Web Server 2 | Reporter: | David Knox <dknox> |
| Component: | tomcat6, tomcat7 | Assignee: | Coty Sutherland <csutherl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jan Stourac <jstourac> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | dwalluck, grocha, jclere, jyundt, myarboro, pslavice, pyaduvan, rsvoboda, sbeal, smumford |
| Target Milestone: | ER03 | Flags: | jclere:
needinfo-
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
In JBoss Enterprise Web Server, some maven-related files for use with Red Hat Enterprise Linux 5, 6, and 7 are still not available in the <filename>tomcat{6,7}-maven-devel</filename> subpackage.
This is a known issue is JBoss Enterprise Web Server 3.0 and no workaround is currently available for this issue.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-04 15:13:03 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
David Knox
2013-08-22 16:12:44 UTC
tomcat6 ep-6 builds are complete Why are they needed? An email bit from David Walluck (dwalluck) <snip> If the problem is that you do not want to ship certain files at runtime, then perhaps we can place the Maven POM and depmap files into a separate subpackage which would not be shipped, such as tomcat-devel. This suggestion doesn't exactly match our usual policy for EAP, but I think it would still work OK if that's the issue. These Maven files are necessary for building in Brew. Various Maven components do request various Tomcat components at build-time. At least in EAP, we do ship the POMs with most packages and always have. The repolib subpackage is only usable for MEAD builds. So, to be clear, this only affects building packages on our own build system and nothing relating to customers, though I believe it to be harmless to provide them. Actually, I am very confused as to when the POMs disappeared. Maybe they were always available in tomcat5 or some other version. I have added pcheung to CC, because I know I have worked with her on EWS in the past and I believe we did have POM files then. Maybe Weinan Li also knows something, but it didn't seem that way given the question. </snip> My concern with including them is that customers often end up using things in ways that we don't think about or intend. Then we take them away at some point and get a complaint. If it's not a problem to put them in another package that we don't ship, I prefer we do that. THX Right now the components are in the corresponding package. I can create a tomcat-devel package for the poms. There are still some maven-related files that were not moved to the tomcat{6,7}-maven-devel subpackage:
RHEL5:
tomcat6-6.0.41-2_patch_01.ep6.el5
tomcat7-7.0.54-4_patch_01.ep6.el5
# rpm -ql tomcat6 tomcat7{,-lib,-el-2.2-api,-jsp-2.2-api,-servlet-3.0-api} | grep maven | sort
/etc/maven/fragments/tomcat6-tomcat-juli
/etc/maven/fragments/tomcat7-tomcat7-websocket
/etc/maven/fragments/tomcat7-tomcat-annotations-api
/etc/maven/fragments/tomcat7-tomcat-api
/etc/maven/fragments/tomcat7-tomcat-catalina
/etc/maven/fragments/tomcat7-tomcat-catalina-ant
/etc/maven/fragments/tomcat7-tomcat-coyote
/etc/maven/fragments/tomcat7-tomcat-el-api
/etc/maven/fragments/tomcat7-tomcat-extras-juli
/etc/maven/fragments/tomcat7-tomcat-extras-juli-adapters
/etc/maven/fragments/tomcat7-tomcat-i18n-es
/etc/maven/fragments/tomcat7-tomcat-i18n-fr
/etc/maven/fragments/tomcat7-tomcat-i18n-ja
/etc/maven/fragments/tomcat7-tomcat-jasper
/etc/maven/fragments/tomcat7-tomcat-jasper-el
/etc/maven/fragments/tomcat7-tomcat-jdbc
/etc/maven/fragments/tomcat7-tomcat-jsp-api
/etc/maven/fragments/tomcat7-tomcat-juli
/etc/maven/fragments/tomcat7-tomcat-servlet-api
/etc/maven/fragments/tomcat7-tomcat-util
/etc/maven/fragments/tomcat7-tomcat-websocket-api
/usr/share/maven2/poms/JPP.tomcat6-tomcat-juli.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat7-websocket.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-annotations-api.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-api.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-catalina-ant.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-catalina.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-coyote.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-el-api.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-extras-juli-adapters.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-extras-juli.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-i18n-es.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-i18n-fr.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-i18n-ja.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-jasper-el.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-jasper.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-jdbc.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-jsp-api.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-juli.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-servlet-api.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-util.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-websocket-api.pom
RHEL6:
tomcat6-6.0.41-1_patch_01.ep6.el6.noarch
tomcat7-7.0.54-4_patch_01.ep6.el6.noarch
# rpm -ql tomcat6 tomcat7 | grep maven | sort
/etc/maven/fragments/tomcat6-tomcat-juli
/etc/maven/fragments/tomcat7-tomcat-juli
/usr/share/maven2/poms/JPP.tomcat6-tomcat-juli.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-juli.pom
RHEL7:
tomcat6-6.0.41-2_patch_01.ep6.el7.noarch
tomcat7-7.0.54-2_patch_01.ep6.el7.noarch
# rpm -ql tomcat6 tomcat7 | grep maven | sort
/etc/maven/fragments/tomcat6-tomcat-juli
/etc/maven/fragments/tomcat7-tomcat-juli
/usr/share/maven2/poms/JPP.tomcat6-tomcat-juli.pom
/usr/share/maven2/poms/JPP.tomcat7-tomcat-juli.pom
|