+1 Gianluca Sartori -- https://dueuno.com
On Tue, 24 Jun 2025 at 20:14, James Daugherty <jdaughe...@apache.org> wrote: > > Hi Everyone, > > As per the discussion [1], we received feedback [2] during our last > grails-core release about how we need to include better instructions on > building our project from a source distribution. The easiest path forward > is to merge grails-forge & grails-core so that the build systems can be > integrated and the same build steps used in CI can be used in the source > distribution. > > This vote proposal is to merge `grails-forge` into the `grails-core` > repository under a `grails-forge` directory. We would use the > includedBuild feature of Gradle to substitute the grails version in the > grails-forge build. This approach allows for a custom version of grails > built from the same source with common build instructions & it keeps the > grails-forge repository isolated under its own gradle build to prevent any > conflicts with Micronaut. Moreover, since we know people have forked forge > to customize it, this allows them to continue to fork from a single > repository if needed. After this change, the grails-forge repository would > be updated to point to the new nested folder under grails-core & archived. > > The vote is open for the next 72 hours and passes if all binding votes are > cast in favor. > > [] +1 proceed with the proposal > [] 0 I don't have a strong opinion about this, but I assume it's ok > [] -1 Do not proceed because ... > > Here is my vote: > > +1 (binding) > > -James > > [1] https://lists.apache.org/thread/w6k2r5nf7l129t5cgc27x00w5ghtjkn5 > [2] https://lists.apache.org/thread/ptkkr19tkrdpmjlx1330cl91l3bbnzvc
