Bug 959702
Summary: | glassfish-servelet-api is required in F19 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | gil cattaneo <puntogil> |
Component: | glassfish-servlet-api | Assignee: | David Xie <davidx> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | davidx, java-sig-commits, mizdebsk |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glassfish-servlet-api-3.1.0-1.fc19 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-15 01:00:11 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: | |||
Bug Depends On: | |||
Bug Blocks: | 859114 |
Description
gil cattaneo
2013-05-04 22:05:45 UTC
There may be some problems with adding glassfish-servelet-api to Fedora 18. I'm not the one to decide, but there are some things to be considered: 1) The Maven artifact that glassfish-servlet-api is javax.servlet : javax.servlet-api. The same artifact is also provided by package tomcat-servlet-3.0-api. In Fedora we generally can't have two versions of the same artifacts unless one of them is a compatibility package. Now the question is which package (tomcat or glassfish) should be the compat package? We shouldn't migrate tomcat-servlet-3.0-api package because that change could cause massive breakage of packages that depend on tomcat-servlet-3.0-api (currently over 60 packages). The only choice is adding glassfish-servlet-api as a compatibility package. This means that merging master to f18 branch is not an option. glassfish-servelet-api would have to be converted to be compatibility package and tested as such. 2) The API itself probably is not very useful if there is no implementation of that API available. Is there Servlet 3.1 implementation available in Fedora 18? 3) Is there any other package besides grizzly that requires the new Servlet API? Why is adding grizzly to Fedora 18 important? Can't grizzly just be built for Fedora 20? 4) Stable release is not right place for development and adding new packages, especially if they may cause problems. Fedora Update Policy [1] explicitly says that "updates should aim to fix bugs, and not introduce features" and "stable releases will not closely track the very latest upstream code for all packages. We have rawhide for that." In my opinion glassfish-servelet-api shouldn't be added to Fedora 18. All development should be done in Fedora 20 (Fedora 19 is after development freeze now). [1] https://fedoraproject.org/wiki/Updates_Policy#Philosophy Agreed. Thank you for your explanation, Mikolaj! glassfish-servlet-api-3.1.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/glassfish-servlet-api-3.1.0-1.fc19 Package glassfish-servlet-api-3.1.0-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glassfish-servlet-api-3.1.0-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12472/glassfish-servlet-api-3.1.0-1.fc19 then log in and leave karma (feedback). glassfish-servlet-api-3.1.0-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |