I think it is reasonable to drop support for older Grails versions on
a regular basis if keeping support hinders maintenance or makes the
plugin work badly.

/Mattias

Den sön 23 aug. 2026 kl 18:31 skrev James Daugherty <[email protected]>:
>
> Hi Everyone,
>
> I've been working on the intellij plugin so we can have our first ASF
> release.  As part of that, several issues were identified.  The main
> blocker is that older versions of Grails included GPL / LGPL code and
> the intellij plugin copied those jar files to support those versions.
> For now, I've gone ahead and referenced them via Maven, but I think we
> should discuss what Grails Versions the IntelliJ plugin should
> actually support.
>
> Are people wanting to maintain legacy Grails support?  Should we
> instead publish a "Legacy Plugin"?  The differences between a Grails
> 1/2 and a Grails 3.3+ app are completely opposite - Grails 3 is what
> introduced the Gradle build system instead of the home grown solution.
>
> I also suspect it's only a matter of time, if not already, that
> IntelliJ itself won't support the java versions or gradle versions
> that older Grails versions need.  Dropping support for anything older
> than Grails 3.3 would greatly simplify the code base.  Splitting the
> plugin into a Grails 1/2 version vs later versions would be another
> alternative.
>
> What do people prefer and what are people willing to support?
>
> -James

Reply via email to