-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated Jetty plugin #735
Comments
I think we have things that use jetty, but not the jetty plugin. Do you think we would need to update things that use jetty (e.g., all of our HTTP/repo mocking infrastructure)? |
We can continue to use Jetty for testing infrastructure. That's totally fine. This work really is only about the fact that were are going to remove the Jetty plugin and therefore need to change everything that depends on it. |
@eriwen Why did you remove the milestone for this issue? The deprecation message and our documentation says that the plugin will be removed with 4.0. |
@bmuschko Mistake on my part. We aren't doing any new deprecations in 4.0, but since this is already deprecated I'll put it back on the 4.0 milestone |
Remember to remove it from the user manual too. |
Closing as complete |
The Jetty plugin has been deprecated with Gradle 3.0. The plugin including all its tests needs to be removed from the Gradle code base. Any testing coding code that relies on the Jetty plugin needs to be changed to use a different solution.
Expected Behavior
Delete the plugin code under
jetty
subproject and anything in the Gradle core infrastructure that uses it.Current Behavior
Users will have to use the external Gretty plugin.
Context
The Jetty plugin in its current form does not provide a good user experience. It uses a very old version which is not configurable. Users expect more functionality of the plugin.
Your Environment
All environments.
The text was updated successfully, but these errors were encountered: