We know that some users fork grails forge to customize it. If we split the forge projects those users would have to fork both core / forge.
-James On Sun, Jun 15, 2025 at 11:41 AM Mattias Reichel <mattias.reic...@gmail.com> wrote: > > Basically, by merging partially, it makes our life easier, and their life > harder. By merging both, we keep it simple for everyone. > > This sentence, puzzles me a bit. > > I think start.grails.org infrastructure code can be kept separate and we > merge only the CLI projects needed for a release. > > /Mattias > > Den sön 15 juni 2025 16:03Søren Berg Glasius <soe...@glasius.dk> skrev: > > > Hi James D et al. > > > > If it eases the release flow, I see no reason why not to merge it all. > > > > I will be +1 in a vote. > > > > Den søn. 15. jun. 2025 kl. 15.59 skrev James Daugherty > > <jdaughe...@jdresources.net.invalid>: > > > > > Hi Everyone, > > > > > > One of the issues we found as part of our release process is that the > > > projects: > > > > > > grails-forge-core > > > grails-forge-cli > > > grails-cli > > > > > > exist in the grails-forge repo. While they exist in a separate repo > > > (grails-forge), we still have to produce a combined source & binary > > > distribution with these artifacts for any grails-core release. This is > > ASF > > > policy. Having a separate repo complicates the release workflow for > > > grails: > > > > > > 1. We have to provide instructions on how to compile both core & forge > > from > > > a source zip. > > > 2. Those instructions ideally use the same build process we use in CI. > > > Since we publish to a shared maven repo, this is currently not possible > > > without a custom build script or change to the local code to publish to > > > maven local. > > > 3. We have to manage a grails release across multiple tags, repos, and > > > workflows. > > > > > > #1 was raised by the groovy PMC as a concern and #2 makes this > > > non-trivial. The concern raised by the groovy PMC is likely to act as > a > > > blocker to future releases if we do not address this (it's an ASF > > > requirement). For this reason, I'd like to discuss merging some or all > > of > > > grails-forge into core. If we merge some, it would only be the > projects > > > that are used in a grails-core release (listed above). If we merge all > > ,it > > > would include the netty, api, etc projects. Even though these projects > > are > > > only used by start.grails.org. > > > > > > What are people's thoughts on merging? Should we merge all or only the > > > ones we need as part of a grails-core release? > > > > > > For my thoughts: I think merging all of the projects is better because > we > > > know some end users fork grails-forge and it would be more convenient > for > > > them to fork one repository instead of 2. Basically, by merging > > partially, > > > it makes our life easier, and their life harder. By merging both, we > > keep > > > it simple for everyone. > > > > > > > > > -- > > > > Med venlig hilsen, > > Søren Berg Glasius > > > > Hedevej 1, Gl. Rye, 8680 Ry > > Mobile: +45 40 44 91 88 > > --- Press ESC once to quit - twice to save the changes. > > >
