James,
Thank you for building a full table based on the thoughts captured in
https://github.com/apache/grails-core/issues/14006 back in Feb. This looks
really good.
My initial thoughts and opinions on the table:
https://github.com/jdaugherty/grails-core/blob/renameProposal/RENAME.md
org.apa
Posting here on behalf of Martyn Duffy:
Hey everyone, I wanted to share an initial take on a new Grails landing page.
Would love your feedback on how to best capture the essence of Grails:
What do we want new visitors to immediately understand about the framework?
What do you think Grails’ uniq
ty
> frameworks such as https://shiro.apache.org/. This convinced me to keep
> the 'spring' in the name to be clear.
>
> Looking at Mattias' revision and comparing it to James Fredley's, I think I
> agree with everything James Fredley has except two points:
>
web-plugin
>| org.apache.grails.profiles | grails-profile-web-plugin
> || |
> grails-profiles|
>
> James Fredley 于2025年3月20日周四 08:43写道：
>
> > Here is a further updated table with the views Gra
/build.gradle#L7
> buildSrc usage:
> https://github.com/apache/grails-views/blob/f9e28f2cfefdc6545f439b72fad15156d5c00781/buildSrc/build.gradle#L29
>
> I'm not proposing we rename the gradle plugin names from your list, but
> rather just that artifact that includes them all
+1
James
On 2025/03/21 21:59:49 James Daugherty wrote:
> Hi Everyone,
>
> As per the [DISCUSS] thread[1], I'd like to propose that we move forward
> with the maven coordinate changes so we can begin snapshot builds under the
> ASF namespace.
>
> I've done my best to capture everyone's feedback
This has had the highest participation of any Grails conversation over the last
~9 months, which is exciting to see.
The goal of this step is to move to Apache groupids, which are required to
setup snapshot publishing at ASF, which will allow us to resume development
with the 18 migrated git re
Welcome. It will be exciting to see Grails 7 released as Apache Grails!
On 2025/03/22 22:45:06 Paul King wrote:
> Lari is a big time past contributor to Grails (second biggest
> contributor to grails-core). He also has a wealth of knowledge about
> many relevant technologies and is involved in nu
18 Grails repositories have been moved to the Apache GitHub organization:
https://github.com/apache?q=grails-&type=all&language=&sort=#org-profile-repositories
On 2025/03/18 12:14:25 James Fredley wrote:
> This move will start today. https://issues.apache.org/jira/browse/INFR
This move will start today. https://issues.apache.org/jira/browse/INFRA-26642
On 2025/03/13 18:13:57 James Fredley wrote:
> A JIRA ticket has been submitted with ASF infrastructure to migrate the
> following repositories to https://github.com/apache/.
>
> https://github.com/g
the orange logo at
the bottom.
James
On 2025/03/19 16:57:43 James Fredley wrote:
> Posting here on behalf of Martyn Duffy:
>
> Hey everyone, I wanted to share an initial take on a new Grails landing page.
> Would love your feedback on how to best capture the essence of Grails:
&g
James Daugherty,
If you have no outstanding concerns with the gradle plug-in, then I have none.
I believe they were addressed in recent days.
For grails-data-mapping, I think local builds times for grails-core should also
be compared. Local will be substantially faster than github runners,
I reviewed the
https://github.com/jdaugherty/grails-core/blob/3b4da92e339b7b688011e4a8ffc3c2aaea723680/RENAME.md?plain=1
iteration and put my approval on the PR.
I am still a little concerned with the artifacts being security-spring and the
project name being spring-security. Matching the upst
I believe is
> > > universally understood to be a "bad idea", yes?
> > >
> > > -Andrew
> > >
> > >> On Fri, Mar 21, 2025 at 8:23 AM Justin Dodson <89web...@gmail.com>
> > wrote:
> > >>
> > >> I tend to le
I have submitted two session topics/papers to the Groovy Track:
- Migrating a 20 year old project to the Apache Software Foundation
- Introduction to Apache Grails 7.1.x
On 2025/02/20 17:20:37 James Fredley wrote:
> Hey Paul,
>
> I am interested in submitting 1 or 2 papers on Grails t
Grails uses the following 3rd party GitHub actions.
PRs have been created to request that the following be added to the allowed
list. See more details on:
https://docs.google.com/document/d/17SdV1nFtIP67Ru8jMQMMZ852PiNaiaiklFNiruQMMu8/edit?tab=t.0#heading=h.3m9yl093tvp8
Note:
You MUST pin all
+1 (binding)
On 2025/04/09 14:35:08 James Daugherty wrote:
> Hi Everyone,
>
> As per the [DISCUSS] thread [1], I'd like to propose we merge the
> grails-views & grails-gradle-plugin repos into the grails-core repo.
>
> The vote is open for the next 72 hours and passes if all binding votes are
>
I really like the idea of the documentation living with the code and am
strongly in favor of this change.
James
On 2025/04/09 14:55:25 James Daugherty wrote:
> Hi Everyone,
>
> We have discussed moving the documentation to grails-core in the past, but
> have held off because the gh-pages bran
+1 (binding)
James Fredley
On 2025/04/11 16:32:38 James Daugherty wrote:
> Hi Everyone,
>
> As per the [DISCUSS] thread [1], I'd like to propose we merge the
> documentation from the grails-doc repository into the grails-core
> repository.
>
> Note: We would continu
With the consensus to this change during the meeting last Thursday and in this
thread, I will send out updated calendar invites for this week and going
forward.
On 2025/04/03 18:40:45 James Fredley wrote:
> The meeting currently takes place at 11am ET on Thursdays or in our common
> time
I have never thought much about the grails-app directory name and do not think
it should change since it does a good job describing the contents.
We should review our documentation around the directory structure, for a Grails
application, to ensure it clearly details the structure and purpose fo
All open issues and PRs from the Grails 7 GitHub project have been added to the
Apache Grails 7.0.x GitHub Project. Close/Done were not added.
All: https://github.com/orgs/apache/projects/487/views/1
By Milestone:
https://github.com/orgs/apache/projects/487/views/2?sliceBy%5Bvalue%5D=grails%3A
+1 (binding)
James Fredley
On 2025/04/18 15:20:04 James Daugherty wrote:
> Hi Everyone,
>
> As per the [DISCUSS] thread [1], I'd like to propose we form a mono repo
> for the "grails-core" libraries by merging the final 2 repositories
> together: grails-geb &
Hi Everyone,
The vote for Changing the Default Branch on
https://github.com/apache/grails-profiles to 7.0.x has passed.
The vote has passed with Five +1 binding votes. Plus two non-binding.
[1] https://lists.apache.org/thread/932bsdygp2gcvbsqnxf2hlh9ws0f7rcb
Hi Everyone,
The vote for Changing the Default Branch on
https://github.com/apache/grails-wrapper to 7.0.x has passed.
The vote has passed with Four +1 binding votes.
[1] https://lists.apache.org/thread/h1ps8jm0vbyn3s48yhqpddvk40ftfrg0
vote is to change the default branch from 6.0.x to 7.0.x.
The vote is open for the next 72 hours.
[] +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 Fredley
branch to 'pre-asf-10.0.x'.
The vote is open for the next 72 hours.
[] +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 Fredley
Hi Everyone,
The vote to Merge grails-profiles & grails-wrapper into grails-core has passed.
The vote has passed with Five +1 binding votes. Plus one non-binding.
[1] https://lists.apache.org/thread/ssmy2lz5hhg7h3zdff0qddpnrkglt7n4
Hi Everyone,
As per the [DISCUSS] int the weekly meeting this morning [1], I'd like to
propose we consolidate grails-profiles & grails-wrapper into grails-core.
grails-core:grails-bom references the versions of grails-profiles and combining
grails-profiles into grails-core allows them to releas
l be addressed with changes before and after these two
projects are merged into grails-core.
I strongly believe that a mono repo is key to quickly iterating on Grails
7.0.x, 7.1.x and 8.0.x, this year.
James Fredley
On 2025/04/17 04:05:31 James Daugherty wrote:
> Hi Everyone,
>
> We&
I think we should proceed with updating the ASF security team on the progress
so we receive updated feedback.
Since we are working on 7.0.0-SNAPSHOT, will most likely need Groovy 4.0.27 for
Grails 7.0.0-M4 and already put the Apache Snapshot Repository in the right
locations to pull Grails SNAP
Previously we solved for the org.gradle:gradle-tooling-api dependency by adding
a remote repo on repo.grails.org so that it is available via
https://repo.grails.org/ui/native/core/org/gradle/gradle-tooling-api/
org.gradle:gradle-tooling-api is currently a dependency on grails-shell-cli only
As
+1 (binding)
James Fredley
On 2025/04/18 15:20:04 James Daugherty wrote:
> Hi Everyone,
>
> As per the [DISCUSS] thread [1], I'd like to propose we form a mono repo
> for the "grails-core" libraries by merging the final 2 repositories
> together: grails-geb &
James,
Thank you for walking through this with me yesterday.
If we look at the collective features and functionality provided across these
tools (grails-shell-cli, grails-wrapper, profiles, grails-forge-cli,
grails-forge-api, start.grails.org, IntelliJ Grails Plugin grails-shell-cli
integratio
I look at forge the same way. The blacksmith forged a sword in his forge.
grails-forge CLI supports the following 16 commands, only. All but "grails
create-functional-test" overlap with grails-shell CLI.
create project commands:
grails create-app
grails create-plugin
grails create-restapi
g
grails-profiles were recently consolidated into a single project to simplify
development and cut 9/10 or more of the time when performing releases.
The web + base profiles has been updated to generate a runnable Grails 7 web
application. Now the other profiles need some additional attention.
T
Example of Apache release voting process with Groovy 4.0.26.
3 days min, unless there are pressing circumstances, such as security patches
for an exploit.
https://lists.apache.org/thread/v31c42n66zkq9bo654bsw01xrf56nhby
. If you would like to be added, just let us know.
On 2025/03/07 02:43:25 James Fredley wrote:
> Hi Everyone,
>
> We meet every week via a google meeting. Each week we will provide a summary
> here to facilitate historical preservation & further discussion. If you
> woul
iliar with the development process for the Apache way,
> do I have to use JIRA to submit the issue first?
>
> James Fredley 于2025年3月7日周五 02:29写道：
>
> > https://github.com/grails/github-actions redirects to
> > https://github.com/grails/grails-github-actions. We will see
Hi Everyone,
We meet every week via a google meeting. Each week we will provide a summary
here to facilitate historical preservation & further discussion. If you would
like to join this meeting, please see:
https://calendar.google.com/calendar/r?eid=MGNnc29hYjFvYW1ndjI5ODJiZXRwZGRjbmMgamFtZX
https://github.com/grails/github-actions redirects to
https://github.com/grails/grails-github-actions. We will see if the following
workflows work or require updates.
https://github.com/search?q=org%3Agrails+grails%2Fgithub-actions%2F&type=code
On 2025/03/06 18:25:53 James Fredley w
https://github.com/gradle/gradle/issues/32558#issuecomment-2697007695
Update from Gradle team on this issue: "This issue needs a decision from the
team responsible for that area. They have been informed. Response time may
vary."
On 2025/02/26 22:38:26 James Fredley wrote:
> I
The following changes have been completed:
Renaming GitHub Repository ✅
If the repository does not start with grails- we need to rename it. ✅
rename gorm implementations (repos) to have ‘grails-data-’ prefix: ✅
rename repo gorm-hibernate5 to grails-data-hibernate5 ✅
rename repo gorm-mongodb to
A JIRA ticket has been submitted with ASF infrastructure to migrate the
following repositories to https://github.com/apache/.
https://github.com/grails/grails-core
https://github.com/grails/grails-gradle-plugin
https://github.com/grails/grails-static-website
https://github.com/grails/grails-plu
+1 to proposed users, commits and notifications mailing lists
And I agree with Soren that we send details to the Google groups directing
subscribers on how to join the Apache Grails mailing lists.
On 2025/02/21 06:14:04 Paul King wrote:
> Hi folks,
>
> Currently Grails has private and dev maili
Thank you for all these details and links.
On 2025/02/21 02:41:05 Paul King wrote:
> Hi folks,
>
> With my mentor hat on, just a reminder of one of the ASF's basic
> principles, meritocracy[1]. Some of you will know this principle well
> or will have heard me talk about it. This email is just to
To setup a custom profile picture for your @apache.org email alias you will
want to create a google account with your @apache.org email alias and then
upload the image on https://myaccount.google.com/. This will display in Gmail
and other Google provided locations.
To setup your profile pict
https://people.apache.org/committer-index.html
On 2025/02/24 22:22:52 Andrew Garcia wrote:
> how does one find their @apache.org email alias?
>
> On Mon, Feb 24, 2025 at 3:10 PM James Fredley
> wrote:
>
> > To setup a custom profile picture for your @apache.org email alias
Hey Paul,
I am interested in submitting 1 or 2 papers on Grails topics, if there is a
Groovy Track at the Conference.
James
On 2025/02/11 22:37:54 Paul King wrote:
> Hi folks,
>
> The ASF has just announced[1] that it will host the North America
> Community Over Code event September 11-14, 2
I submitted an issue (feature request) to add a new strategy to resolve
duplicates consistently for zip/jar/war destinations:
https://github.com/gradle/gradle/issues/32558
You can add me to the moderators list.
James
On 2025/02/24 23:58:20 Paul King wrote:
> I created (still pending with a 12-24 hr delay) the lists with the
> default list behavior which lets subscribers post but others are
> moderated.
>
> It would be good to have a few PPMC folks to help moderate
https://github.com/grails/grails-forge/issues/496
For this issue I need input on the right way to approach building the
grails-forge CLI from the grails-shell CLI project and including it in the
graalvm native binaries. My experience is limited in these areas and if I can
get a running head st
Actually it is the flip, building the grails-shell CLI from the grails-forge
CLI project.
On 2025/02/25 16:39:32 James Fredley wrote:
> https://github.com/grails/grails-forge/issues/496
>
> For this issue I need input on the right way to approach building the
> grails-forge CLI fro
+1 (binding)
James
On 2025/04/03 19:34:52 James Daugherty wrote:
> Hi Everyone,
>
> As per the [DISCUSS] thread [1], I'd like to propose we merge the
> grails-cache repo into the grails-core repo.
>
> The vote is open for the next 72 hours and passes if all binding votes are
> cast in favor.
>
I put a number of related details in my longer post. In terms of location of
the word `plugin` in the artifactid, I prefer towards the beginning vs at the
end. This makes grouping and search a bit simpler. I we go this direction, we
need to make decisions on grails-view-plugin-, grails-gradle
The meeting currently takes place at 11am ET on Thursdays or in our common time
zones:
https://www.worldtimebuddy.com/?qm=1&lid=8,6,5,12,30,1819729,2207259&h=8&date=2025-4-3&sln=8-9&hf=1
There is a request to move the meeting to a day other than Thursday, by one of
the core committers and PPMC
I am in favor of merging Grails Cache into grails-core. This is the right time
do it, since the maven coordinated are changing and on the old coordinates we
were on version 9.0.x which was higher than 7.0.x for grails-core. For this I
think we should have a vote thread just for grails-cache st
This week is the early week.
Google Meet Link is always: https://meet.google.com/her-tjpt-xmf
Notes:
https://docs.google.com/document/d/1L590r6Z_xNQ48l31Yolsir75dUgAorEnTWmW1kGqJrw/edit?tab=t.0#heading=h.yzvjivh6d3yb
Meeting Time:
This week:
https://www.worldtimebuddy.com/?qm=1&lid=8,6,5,12,
Given the current timeline for Grails 7.0.0-RC1 and 7.0.0 and the overlapping
Spring Boot 3.5.x timeline, we should consider bumping the Spring Boot version
for Grails 7.0.x to 3.5.x.
https://spring.io/blog/2025/04/25/spring-boot-3-5-0-RC1-available-now
I don't believe this will introduce any
This looks good, Paul.
I am not sure if the following items rise to the level of importance of the
board report for Grails, but if they do please include them.
- The Grails team continues to hold weekly 1-1.5 hours video meetings to drive
progress
- Important communication, including multiple v
This week is the later time week.
Google Meet Link is always: https://meet.google.com/her-tjpt-xmf
Notes:
https://docs.google.com/document/d/1L590r6Z_xNQ48l31Yolsir75dUgAorEnTWmW1kGqJrw/edit?tab=t.0#heading=h.yzvjivh6d3yb
Meeting Time:
This week:
https://www.worldtimebuddy.com/?qm=1&lid=8,6,5,
We are very close and it has taken a gargantuan amount of effort to prepare for
the first Apache Grails milestone.
I agreed with the list under "the following needs completed" and think these
two items should be part of that list, for clarification.
# grails-forge will be staged for release
Some additional relevant details for Grails 7 & 8 and hibernate 5, 6 and 7:
https://github.com/apache/grails-core/discussions/13521#discussioncomment-12451797
On 2025/05/23 03:35:36 Walter Duque de Estrada wrote:
> So I would like to propose to make the current Hibernate 6 branch the Grails
>
+1 (binding)
James Fredley
On 2025/06/03 00:23:20 James Daugherty wrote:
> Hi Everyone,
>
> I am happy to start the VOTE thread for an Apache Grails (incubating)
> release of version 7.0.0-M4!
>
> This release is our first release under the ASF. Further details of the
> re
The Apache Grails (incubating) community is pleased to announce the
release of the Grails Plugins: Redis 5.0.0-M4 & Spring Security
7.0.0-M4.Grails is a powerful Groovy-based web application framework
for the JVM built on top of Spring Boot that has many plugins to
further extend its functional
being updated to 3
- similar changes are required in Grails Shell CLI:
https://github.com/apache/grails-core/issues/13752
James Fredley
/grails-static-website/issues/356
The vote is open for the next 72 hours
[] +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 Fredley
Thank you.
+1 (binding)
James Fredley
On 2025/06/24 18:14:40 James Daugherty 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 sour
and review.
James Fredley
On 2025/06/16 19:28:18 James Daugherty wrote:
> 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 gr
start.grails.org in the grails-forge
repository.
grails-forge-analytics-postgres
grails-forge-api
grails-forge-web-netty
James Fredley
On 2025/06/15 13:59:15 James Daugherty wrote:
> Hi Everyone,
>
> One of the issues we found as part of our release process is that the
> projects:
After reviewing
https://blog.pragmaticengineer.com/stack-overflow-is-almost-dead/, the decline
at StackOverflow is rapid and nearly total/fatal.
Based on this we should guide users to post questions in the users mailing
list. GitHub discussions can be an alternative, since it is replicated to
That sounds logical and will allow the vote to commence ASAP.
On 2025/06/09 15:26:40 James Daugherty wrote:
> Hi Everyone,
>
> I've opened https://github.com/apache/grails-spring-security/pull/1116 that
> will fix the remaining test failures in Grails Spring Security. Note: that
> the latest ver
numerous discussions about converting the
forge-api project from a Micronaut App to a Grails app and I think this could
happen for Grails 8+
James Fredley
On 2025/06/15 13:59:15 James Daugherty wrote:
> Hi Everyone,
>
> One of the issues we found as part of our release process is
Hi Everyone,
The vote to Redirect https://grails.org/ to https://grails.apache.org/
has passed.
The vote has passed with FOUR +1 binding votes plus TWO +1
non-binding votes.
I will proceed with creating a PR to complete the necessary changes
detailed on: https://github.com/apache/grails-stat
+1 (binding)
Thank you for working into the early hours of the morning to get this restaged.
James Fredley
On 2025/06/04 08:44:46 James Daugherty wrote:
> Hi Everyone,
>
> We have fixed the shell CLI issue with profiles & dynamic command lookups
> so I am happy to start the new
Mattias has begun work on the Headers & License updates for Grails Spring
> Security. When this work is complete, we'll need to do something similar
> to `grails-core` so we can publish the Grails Spring Security plugins. My
> assumption is we'll hold the Grails 7.0.0-M4
+1 (binding)
On 2025/06/12 02:42:12 James Daugherty wrote:
> Hi Everyone,
>
> I am happy to start the VOTE thread for Apache Grails (incubating) Plugins
> - Spring Security 7.0.0-M4 & Redis 5.0.0-M4!
>
> We are releasing these plugins together as they are dependent on each
> other. At a high lev
[] 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 Fredley
+1 binding
James Fredley
On 2025/07/09 15:36:27 James Daugherty wrote:
> Hi Everyone,
>
> I am happy to start the VOTE thread for an Apache Grails (incubating)
> release of version 7.0.0-M5!
>
> Pre-release discussion thread is here:
> https://li
+1 binding
James
On 2025/07/02 15:58:16 James Daugherty wrote:
> Per discussion [1] and the unanimous feedback in the weekly meeting, I'd
> like to propose we revert to Sitemesh 2.x for Grails 7. Please see the
> thread for the reasons, but the initial work is here:
> https://github.com/apache/g
aused by Sitemesh 3
changes made before the majority of dependencies were updated for Grails 7 in
Summer and Fall 2024.
James Fredley
On 2025/07/02 11:38:52 James Daugherty wrote:
> Hi Everyone,
>
> I started investigating a ticket related to forwarding not working in a
> Gra
+1 (binding)
James Fredley
On 2025/06/30 17:09:33 James Daugherty wrote:
> Hi Everyone,
>
> As per discussion [1], I am proposing we split the Grails Publishing gradle
> plugin into its own repo with its own release cycle. This includes
> publishing this plugin to the gradl
Unlocking the ability to use it in grails-core is enough reason, from my
perspective.
Everything else is gravy.
James Fredley
On 2025/06/27 13:29:34 James Daugherty wrote:
> Hi Everyone,
>
> The Grails Publish Plugin does not have any dependencies on Grails or our
> code. Afte
y default in Grails 5 and grails shell (profile based)
generated applications in 6.2.1+, including 7.0.x
c. James Fredley will adjust it to be default from forge also
i. Users with larger projects are more likely to know to remove it
10. database migration plugin
a. some scripts are missing
b. https://github.com/apache/grails-core/issues/14918
+1 (binding)
Plus was missing
On 2025/07/24 16:11:49 James Fredley wrote:
> 1 (binding)
>
> James Fredley
>
> On 2025/07/24 15:48:55 James Daugherty wrote:
> > Hi Everyone,
> >
> > I am happy to start the VOTE thread for Apache Grails (incubating)
> >
1 (binding)
James Fredley
On 2025/07/24 15:48:55 James Daugherty wrote:
> Hi Everyone,
>
> I am happy to start the VOTE thread for Apache Grails (incubating)
> Plugin - Redis 5.0.0-M5!
>
> At a high level, this plugin is being updated to support the
> recent Grails 7.0.
+1 (binding)
James Fredley
On 2025/07/24 15:51:17 James Daugherty wrote:
> Hi Everyone,
>
> I am happy to start the VOTE thread for Apache Grails (incubating)
> Plugin - Spring Security 7.0.0-M5
>
> At a high level, this plugin is being updated to support the
> recent Gr
+1 (binding)
James Fredley
On 2025/07/25 15:31:38 James Daugherty wrote:
> Hi Everyone,
>
> I am happy to start the VOTE thread for Apache Grails (incubating)
> Plugin - Quartz 4.0.0-M3
>
> At a high level, this plugin is being updated to support the
> recent Grails 7.0.
88 matches
Mail list logo
