apache / apache/grails-core

Suggestion for Grails 5+: supersede/deprecate some of the grails-gradle-plugin features with Gradle native implementation

Open
#14,149 2 comments 3 reactions 0 assignees View on GitHub
relates-to: gradle-plugin
Dominant language
Groovy
Stars
2.9k
Forks
975
Avg merge
1d 22h
Merged PRs (30d)
92

Description

I believe some of the grails-gradle-plugin features can now be used with Gradle natively. To be future proof and reduce maintenance I think it would be nice to rewrite some of the current grails-gradle-plugin implementation with the Gradle native variants.

Some examples:
- remove pathingJar as this is now implemented in Gradle itself
- I think the exploded classpath (for multi-module projects) could be replaced by Gradle's variant attributes
- with variant attributes the Grails specific plugin-dependencies block could surely be dropped (use the standard Gradle dependency block)

Contributor guide

Open the contributing guide

Research direction

Start by examining the grails-gradle-plugin implementation for pathingJar, the exploded classpath, and the Grails-specific plugin-dependencies block. Compare each feature with Gradle's native implementation and variant attributes; done means an agreed, tested plan to supersede or deprecate the redundant features.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
build-system
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.