I'll create the vote thread then. thanks everyone.
On Tue, Jun 24, 2025 at 1:02 AM Mattias Reichel
wrote:
> By all means, let's put it in a nested project.
>
> Den mån 23 juni 2025 kl 22:27 skrev James Fredley >:
>
> > After a few conversations with James Daugherty, I think bringing all 6
> >
By all means, let's put it in a nested project.
Den mån 23 juni 2025 kl 22:27 skrev James Fredley :
> After a few conversations with James Daugherty, I think bringing all 6
> grails-forge subprojects over to grails-core is the best approach for the
> following reasons:
>
> - We are limited on tim
After a few conversations with James Daugherty, I think bringing all 6
grails-forge subprojects over to grails-core is the best approach for the
following reasons:
- We are limited on time and need to complete this consolidation before the
next milestone or release candidate and it take materia
These are the dependencies between the Grails Forge and Grails Core
projects:
grails-forge-core
└── org.apache.grails.profiles:base (grails-core) (build dependency for
copying grails-wrapper files from base profile to generated applications)
grails-forge-cli
└── grails-forge-core
grails-cli
├──
My opinion is that we should merge only the projects related to the
Grails distribution. Projects needed to build the forge web
application can stay in another repository.
Gianluca Sartori
--
https://dueuno.com
On Sun, 15 Jun 2025 at 15:59, James Daugherty
wrote:
>
> Hi Everyone,
>
> One of the
I'm not familiar enough with the use cases for third parties forking Grails
Forge to assess the strength of this argument.
Do what you think is best. I'm confident it will work out fine either way.
Den lör 21 juni 2025 01:17James Daugherty
skrev:
> @Mattias what are your thoughts here? I was t
@Mattias what are your thoughts here? I was thinking of starting a vote,
and want to make sure everyone agrees.
On Mon, Jun 16, 2025 at 4:00 PM James Fredley
wrote:
> After discussing this further this afternoon, I have changed my opinion
> from splitting grails-forge in half and am now onboard
After discussing this further this afternoon, I have changed my opinion from
splitting grails-forge in half and am now onboard with bringing the whole
grails-forge project over as a sub gradle project in grails-core.
Splitting it in half was convenient for grails development volunteers, but
wou
I discussed this more with James F to see if we can find other solutions.
I still think we should bring the full thing over.
Some other thoughts:
1. I am proposing we merge grails-forge as a sub gradle project to
grails-core only to facilitate easier publishing / building. This means
locally ther
I lean towards merging the following 3 project into grails-core to simplify the
release process and review during the release vote.
grails-forge-core
grails-forge-cli
grails-cli
And leaving the following, which are only used for the next.grails.org,
snapshot.grails.org, etc. instances by start.
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
wrote:
> > Basically, by merging partially, it makes our life easier, and their life
> harder. By
> 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.
/Mattia
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
:
> Hi Everyone,
>
> One of the issues we found as part of our release process is that the
> projects:
>
> grails-forge-core
>
13 matches
Mail list logo
