#422 move an existing package to a different upstream fork
Closed: Fixed None Opened 5 years ago by pmackinn.

I maintain an existing [http://koji.fedoraproject.org/koji/packageinfo?packageID=16449 jspc compiler plugin package] in Fedora. I'm wondering if it is (going forward) permissible to make use of a different upstream fork within that package.

Neither is canonical, since the Eclipse project owns Jetty which has reintroduced the plugin in version 9.x. However, the latest Jetty 9 series can strictly only be used with Java 7 and we would like to maintain Java 6 compatibility with the Hadoop upstream project.

The motivation for the change is that the current version relies on groovy and ant integration which has repeatedly caused problems with Fedora version updates. The proposed version is groovy-free. Also, it appears to have support for Tomcat 7 (the current version in Fedora) which the existing jspc upstream never did.

The codehaus upstream development is defunct while the fork at github has had a few pull requests in the past 12 months.


Precedent is that this is fine but it goes through the Fedora Change Process to be approved. I think the deadline for F21 has already passed but you can propose it anyway and see if fesco will make an exception.

Login to comment on this ticket.

Metadata