[GRADLE-723] allow override of dependencies used by plugins Created: 29/Oct/09  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.8
Fix Version/s: None

Type: Improvement
Reporter: Marcus Better Assignee: Unassigned
Resolution: Won't Fix Votes: 5


Sometimes it is useful to replace a bundled dependency, like Jetty, with a newer version, if the build requires some new feature. See discussion at <http://permalink.gmane.org/gmane.comp.programming.tools.gradle.user/2622>.

Comment by Pekka Mattila [ 11/Nov/09 ]

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.

Comment by Hans Dockter [ 22/Nov/09 ]

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

Comment by Cédric Champeau (Inactive) [ 24/Jul/12 ]

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.

Comment by Peter Niederwieser [ 24/Jul/12 ]

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.

Comment by Cédric Champeau (Inactive) [ 24/Jul/12 ]

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...

Comment by Benjamin Muschko [ 15/Nov/16 ]

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!

Comment by Benjamin Muschko [ 16/Jan/17 ]

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.

Generated at Wed Jun 30 11:37:11 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.