Description of problem: Jetty 9 changed their Connector classes requiring significant work to port to it. Additionally, jetty 9 does not appear to api stable because jetty 9.1.0 broke some bits that worked with jetty 9.0.x. Upstream projects that use jetty may resist updating to jetty 9 because jetty 9 will not work on java 6. It seems to make sense to create and maintain a jetty 8 compat package for these reasons. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We've had Jetty 9.x since F19. So far the only package needing it for building was maven-site-plugin which we migrated to jetty 9. I'll put it this way: I hate compat packages with all my heart and certainly don't want to see more of them in Fedora. I won't stop others from packaging them (that's why we made it easier) but I won't do it myself unless I am held at a gunpoint. Also: whenever there's a compat package, there should be a migration strategy/plan to get all the packages to newer version of dependencies. I think it will be hard to find this for upstreams that intend to stay at Java 6 If you *really* want to see Jetty 8.x in Fedora you'll probably have to package and maintain it yourself. This is not a bug in jetty package so closing