This would be very important when implementing, for example, a comet enabled application using cometd-java and Jetty 7. Currently it's not possible to replace the old Jetty 6.1x with Jetty 7, which is a must for Comet application development.

This is an important feature and will be made available by our future classloader isolation (the release after 0.9, whatever that will be).

Is there a way to do this with Gradle 1.0? I need to test a new bnd version which works with invokedynamic but I can't find how to change the version of the tool which is used by the osgi plugin.

I don't know of a way to do this in Gradle 1.0. Workarounds are to patch the Gradle distribution or to use bnd directly (maybe there is an Ant task?), instead of or in addition to the osgi plugin.

Ah, too bad. It's a bit overkill to have a custom version of Gradle to release Groovy. Let me see if I can fork the plugin only and give it another name...

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

The Jetty plugin has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore.