Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
ort grails-views > > org.grails views-markup org.apache.grails.plugins > grails-view-plugin-markup > > grails-views > > IMO we should decide where the word *plugin* is placed in the name. > > Personally I'd prefer *grails-x-plugin*, and *grails-view-x-plugin* (so >

Grails Repositories Migrated - Next Steps - Snapshot Builds

2025-03-18 Thread James Daugherty
Hi Everyone, A small update on the status of the migration effort: - Repositories have been migrated. - Infrastructure will work on providing credentials for snapshot builds tomorrow. - Next, we will need to update the snapshot builds to use those credentials. - Future, we need

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
-spring-security-oauth2 > > org.apache.grails:grails-spring-security-rest > > org.apache.grails:grails-spring-security-rest-data > > org.apache.grails:grails-spring-security-rest-grails-cache > > org.apache.grails:grails-spring-security-rest-memcached > > org.apache.gra

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
gt; > James Fredley 于2025年3月20日周四 08:43写道: > > > > > Here is a further updated table with the views Gradle plugins > consolidated > > > into grails-gradle-plugin, which is renamed back to its original name. > > > This update also moves grails-test to the correct grou

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-20 Thread James Daugherty
I don't think we should rename any repositories until builds are fully working. It will delay the 7 release process otherwise. The goal of this discussion is specific to the groupid / artifactid. On Thu, Mar 20, 2025 at 12:46 PM Gianluca Sartori wrote: > Yes, I am just talking about the reposi

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-20 Thread James Daugherty
@Gianluca, were you ok with the latest draft? https://github.com/apache/grails-core/pull/14080 On Thu, Mar 20, 2025 at 12:56 PM Gianluca Sartori wrote: > Okay sounds good > > Gianluca > > > On Thu, 20 Mar 2025 at 17:52, James Daugherty > wrote: > > > I do

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-20 Thread James Daugherty
I updated the PR to include Robert's feedback. On Thu, Mar 20, 2025 at 11:07 AM Robert Oschwald wrote: > Just my 2c: > > grails-data-hibernate[5|6]-migration I would name > grails-data-hibernate[5|6]-dbmigration > > > > > Am 20.03.2025 um 15:54 sch

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-21 Thread James Daugherty
ier to read? On Fri, Mar 21, 2025 at 11:02 AM Mattias Reichel wrote: > > Did you mean to say artifact ids instead of groupIds? > > Yes, sorry for the confusion, I meant artifactIds. > > Den fre 21 mars 2025 kl 15:55 skrev James Daugherty > : > > > 1. Did you mean to

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-21 Thread James Daugherty
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. Mat

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-21 Thread James Daugherty
I updated the PR. On Fri, Mar 21, 2025 at 1:02 PM Mattias Reichel wrote: > Thank you James! > My question was more regarding why two of them are collapsed: > - databinding > - datastore > vs non-collapsed: > - data-mapping > > Den fre 21 mars 2025 kl 17:30 skrev James

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-21 Thread James Daugherty
it as 'grails-data' On Fri, Mar 21, 2025 at 12:07 PM Mattias Reichel wrote: > Excuse a non-native english speaker, should these be treated the same or > differently? > databinding > datamapping > datastore > > Den fre 21 mars 2025 kl 16:38 skrev James Daugherty > :

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-21 Thread James Daugherty
s-rest-transforms groupId: event -> events groupId: view -> views This assumes a plural form to match existing grails convention in package names & groupids. On Fri, Mar 21, 2025 at 11:11 AM James Daugherty wrote: > Thank you. I'd rather we hyphenate all words in the artifact id. I

[VOTE] Group Id, Artifact Id rename + Views Gradle Plugins Proposal

2025-03-21 Thread James Daugherty
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 under the pull request for this proposal here: https://github.com/apach

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-21 Thread James Daugherty
that work to restore snapshot publishing can > begin early next week after the 72 hour vote window. Nothing is set in > stone. > > James > > On 2025/03/19 12:44:48 James Daugherty wrote: > > Hi Everyone, > > > > Per previous meetings, we agreed to rename the

[RESULT][VOTE] Group Id, Artifact Id rename + Views Gradle Plugins Proposal

2025-03-24 Thread James Daugherty
Hi Everyone, I realized I replied to the thread instead of starting a new one. Resending here: The vote has passed with FIVE +1 binding votes. There was one abstaining binding vote and FOUR +1 non-binding votes. We'll proceed this week with getting snapshot builds setup. The goal is to have th

Re: [VOTE] Group Id, Artifact Id rename + Views Gradle Plugins Proposal

2025-03-24 Thread James Daugherty
05 PM Michael Yan wrote: > I withdraw my veto. My vote is 0. > > On 2025/03/22 03:00:08 Michael Yan wrote: > > [-1],specifically, I disagree with 1, 2, 10 > > > > On Sat, Mar 22, 2025 at 6:02 AM James Daugherty > > wrote: > > > > > Hi Everyone, &g

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
`plugins {id version}`? The > long groupid and artifactid is only used for `plugins {id version}`. > > James > > On 2025/03/19 23:23:57 James Daugherty wrote: > > Mattias made a good point in his open PR: there are other security > > frameworks such as https://shi

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
Forgot, there was one more too: grails-security-plugin (note the drop of "spring"). On Wed, Mar 19, 2025 at 9:34 AM James Daugherty wrote: > If we treat the keyword as a prefix, it is easier to find them on maven > central. These were the prefixes being suggested: > > g

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
rails-spring-security-rest-grails-cache > org.apache.grails:grails-spring-security-rest-memcached > org.apache.grails:grails-spring-security-rest-redis > org.apache.grails:grails-spring-security-ui > > org.apache.grails:grails-redis > org.apache.grails:grails-quartz > > Regards &g

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
e to prefix the artifact ids to ensure the jar names never overlapped. On Wed, Mar 19, 2025 at 12:22 PM James Daugherty wrote: > How do we distinguish between the implementation and the exposure of that > implementation? Take for example hibernate5 - there's an implementation of > gra

[DISCUSS] Group Id & Artifact Id Renames

2025-03-19 Thread James Daugherty
Hi Everyone, Per previous meetings, we agreed to rename the maven coordinates as part of transitioning to the ASF. During this renaming, we also set out several requirements for being consistent with our group ids and artifact ids. Since these renames are going to be referenced heavily by anyone

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-20 Thread James Daugherty
| > > || grails-views | > > | org.grails.plugins | gsp > >| org.apache.grails | > > grails-views-gsp | > > |

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-04-05 Thread James Daugherty
s > IMO we should decide where the word *plugin* is placed in the name. > Personally I'd prefer *grails-x-plugin*, and *grails-view-x-plugin* (so > *grails-fields-plugin* and *grails-view-gsp-plugin* for examples and > perhaps *grails-view-core*) for consistency. > >

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-04-05 Thread James Daugherty
he command templates. > > https://github.com/apache/grails-profiles/issues/5 > > James Daugherty 于2025年3月20日周四 09:22写道: > > > James Fredley: I am good with your proposal. > > > > Søren, Mattias, Michael, and Gianluca - does James’s updated version work > >

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-04-05 Thread James Daugherty
ecurity-spring-* is a good idea! > > > > > Why don't we make anything that is a plugin have a root group id of > > "org.apache.grails", and anything that's supportive have a nested group > > name based on the type? > > I think this is worth explor

Re: [DISCUSS] Grails-cache merger to grails-core

2025-04-05 Thread James Daugherty
hy not merge > them all together? > > On 2025/04/02 17:35:28 James Daugherty wrote: > > Hi Everyone, > > > > As we discussed in last week's weekly meeting, we have a desire to merge > > grails-cache into grails-core. We want to continue to merge repositories > &

[Weekly Developer Meeting] - 2025/04/03 - Notes

2025-04-05 Thread James Daugherty
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 let us know. Notes for this week follow: - We are planning to move the weekly developer meeting time so

Re: Grails Hibernate 6

2025-04-05 Thread James Daugherty
The intention was to merge it in after its buildable. I would leave it separate for now. I intend to make time in May to assist on that project. On Sat, Apr 5, 2025 at 5:34 PM Walter Duque de Estrada wrote: > Dear Grails contributors: > > I have been working on updating grails for hibernate 6

Re: [DISCUSS] Grails-cache merger to grails-core

2025-04-04 Thread James Daugherty
nd like people have concerns with data mapping (build times) and the gradle plugin. James, can you clarify your concern with the gradle plugin? For data mapping, are build times in GitHub the only concern people have? Regards, James On Thu, Apr 3, 2025 at 2:01 PM James Daugherty wrote: &g

Re: [DISCUSS] grails-doc to grails-core

2025-04-09 Thread James Daugherty
2025 kl. 17.18 skrev Gianluca Sartori > : > >> +1 >> >> Gianluca Sartori >> >> >> >> On Wed, 9 Apr 2025 at 16:57, James Daugherty >> wrote: >> >>> Hi Everyone, >>> >>> We have discussed moving the documentat

[VOTE] merge grails-views & grails-gradle-plugin repositories into grails-core

2025-04-09 Thread James Daugherty
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 cast in favor. [] +1 proceed with the proposal [] 0 I don't have a strong

Re: [DISCUSS] Grails-cache merger to grails-core

2025-04-10 Thread James Daugherty
I am not seeing any objections so I'll move forward with a vote thread for views & grails-gradle-plugin. On Sat, Apr 5, 2025 at 12:36 PM James Fredley wrote: > > James Daugherty, > > If you have no outstanding concerns with the gradle plug-in, then I have > none. I bel

[DISCUSS] grails-doc to grails-core

2025-04-10 Thread James Daugherty
Hi Everyone, We have discussed moving the documentation to grails-core in the past, but have held off because the gh-pages branch is very large since it contains the history of documentation. I'd like to propose we move only the current docs (not the published versions) to grails-core. Some imme

Re: [DISCUSS] grails-doc to grails-core

2025-04-11 Thread James Daugherty
The responses are overwhelmingly positive so I'll start a vote thread. On Wed, Apr 9, 2025 at 11:33 AM James Daugherty wrote: > To be clear, we would continue to publish the docs to grails-doc. We just > would have the docs live with the code. > > > On Apr 9, 2025, at

[VOTE] merge grails-doc to grails-core repository

2025-04-11 Thread James Daugherty
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 continue to publish the generated documentation to the grails-doc gh-pages branch due to the historical size of the generated

[Weekly Developer Meeting] - 2025/04/09 - Notes

2025-04-11 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

[RESULT][VOTE] merge grails-cache repository into grails-core

2025-04-07 Thread James Daugherty
Hi Everyone, The vote for merging the grails-cache repo into grails-core[1] has passed. The vote has passed with FIVE +1 binding votes. There was one ONE +1 non-binding vote. We'll proceed with getting the grails-cache repository merged in the coming week. [1] https://lists.apache.org/thread/r

[VOTE] Merge Grails-geb & Grails-data-mapping to form a mono repo

2025-04-18 Thread James Daugherty
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 & grails-data-mapping. The vote is open for the next 72 hours and passes if all binding votes are cast in favor. [] +1 pr

Re: [DISCUSS] Merge Grails-geb & Grails-data-mapping to form a mono repo

2025-04-18 Thread James Daugherty
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, >

Re: [VOTE] Change Default Branch on https://github.com/apache/grails-wrapper to 7.0.x

2025-04-18 Thread James Daugherty
+1 (binding) On Fri, Apr 18, 2025 at 6:19 PM James Fredley wrote: > Hi Everyone, > > With the change to Apache Grails maven coordinates, we are moving > grails-wrapper to version 7.0.x to match the Grails version. ASF requires a > vote to change the default branch. > > See: https://github.com/ap

Re: [VOTE] Change Default Branch on https://github.com/apache/grails-profiles to 7.0.x

2025-04-18 Thread James Daugherty
+1 (binding) On Fri, Apr 18, 2025 at 5:34 PM James Fredley wrote: > Hi Everyone, > > With the change to Apache Grails maven coordinates, we are moving profiles > back to version 7.0.x to match the Grails version. ASF requires a vote to > change the default branch. We were on Version 10.0.x due

Re: [DISCUSS][HELP] Reproducible Builds

2025-04-28 Thread James Daugherty
ignore } } On Sat, Apr 26, 2025 at 5:32 AM Jochen Theodorou wrote: > On 24.04.25 23:06, James Daugherty wrote: > [...] > > I'm planning to continue researching this, but if anyone has experience > > with the AST transforms or the ordering problem, it would be helpful to >

[Weekly Developer Meeting] - 2025-04-16 - Notes

2025-04-23 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

[RESULT][VOTE] merge grails-doc to grails-core repository

2025-04-14 Thread James Daugherty
Hi Everyone, The vote for merging the grails-doc repo into the grails-core repo[1] has passed. The vote has passed with THREE +1 binding votes. There were TWO +1 non-binding votes. We'll proceed with getting this merged in the coming week. [1] https://lists.apache.org/thread/q4575m02xh9brfvmp8

[DISCUSS] Merge Grails-geb & Grails-data-mapping to form a mono repo

2025-04-16 Thread James Daugherty
Hi Everyone, We've previously discussed [1] merging the grails-data-mapping repo into grails-core. Other than grails-geb, this is the last remaining repository to merge into core to have a mono repo. This email attempts to summarize some of the previously expressed concerns and advocates for merg

Re: [DISCUSS] Handling org.gradle:gradle-tooling-api which is not published to mavenCentral

2025-05-05 Thread James Daugherty
t; I guess a fresh start for Grails 7+ artifacts would not hurt given the age > and state of that repository. > > Den lör 3 maj 2025 kl 14:47 skrev James Daugherty > : > > > @Mattias, what are your thoughts about creating a new repository on > > repo.grails.org to isolate legacy a

Re: [DISCUSS][HELP] Reproducible Builds

2025-05-05 Thread James Daugherty
anent solution, but for the Milestone / RC builds, I think it's acceptable. -James On Mon, Apr 28, 2025 at 10:15 PM James Daugherty wrote: > Hi Everyone, > > I summarized my progress thus far under this ticket: > https://github.com/apache/grails-core/issues/14679 > > I chec

Re: [DISCUSS][HELP] Reproducible Builds

2025-05-05 Thread James Daugherty
SHOT last year, but the root causes for those issues are addressed in > grails-core. > > I also think it would be fine to merge and then start a new PR once > addition updates can be made. > > On 2025/05/05 16:11:22 James Daugherty wrote: > > Paul was able to fix the groovydoc

IDE Lockups in Core

2025-05-05 Thread James Daugherty
FYI: I reached out to Jetbrains support: if you have the grails plugin enabled in IntelliJ and try to use grails-core it will cause the source files to not be browseable. https://youtrack.jetbrains.com/issue/IDEA-366647 is the upstream ticket. I've updated our internal tracking ticket as well: http

[Weekly Developer Meeting] - 2025-04-30

2025-05-05 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

Re: [DISCUSS][HELP] Reproducible Builds

2025-05-06 Thread James Daugherty
e are objections. -James On Mon, May 5, 2025 at 9:08 PM James Daugherty wrote: > To go back to security fully, I think we'll need to make a script that > downloads the jars, builds locally, and then compares. Currently the > script locally just builds twice and compares. > &g

[DISCUSS] grails-forge publishing requirements

2025-05-06 Thread James Daugherty
Hi Everyone, James F & I have been discussing the ASF release process. I've previously mentioned that we have to have reproducible builds to use GitHub actions. We have made the discovery that it's impossible to have reproducible builds in forge due to this bug: https://github.com/oracle/graal/i

[DISCUSS][HELP] Reproducible Builds

2025-04-24 Thread James Daugherty
Hi Everyone, As part of being given permission to publish a release under the ASF, we have to meet the requirements of the ASF for publishing builds. During our security audit, the following was noted: - BEGIN QUOTE -- One thing that I didn't see explicitly called out is 'how' to revie

Re: [VOTE] Merge grails-profiles & grails-wrapper into grails-core

2025-04-23 Thread James Daugherty
+1 (binding) On Wed, Apr 23, 2025 at 3:00 PM James Fredley wrote: > 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-

[Weekly Developer Meeting] - 2025-04-23 - Notes

2025-04-23 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

[RESULT][VOTE] merge grails-views & grails-gradle-plugin repositories into grails-core

2025-04-12 Thread James Daugherty
Hi Everyone, The vote for merging the the grails-views & grails-gradle-plugin repos into the grails-core repo[1] has passed. The vote has passed with FOUR +1 binding votes. There were THREE +1 non-binding votes. We'll proceed with getting these merged in the coming week. [1] https://lists.apac

Re: [DISCUSS][HELP] Reproducible Builds

2025-04-28 Thread James Daugherty
ood news is the scripts I've checked in can be used to "verify" that the jars were built correctly - we can build locally and manually diff the artifacts to confirm they're correct. This is the work around I plan to suggest to ASF security. -James On Mon, Apr 28, 2025 at 11:5

Re: [DISCUSS] Handling org.gradle:gradle-tooling-api which is not published to mavenCentral

2025-05-03 Thread James Daugherty
#x27;ve provided, but also to make Grails more future > > proof and communicate it as more "integrated" with relevant technologies > > (if that makes any sense, it does in my mind). > > > > Gianluca Sartori > > -- > > https://dueuno.com > &g

Re: [DISCUSS] Handling org.gradle:gradle-tooling-api which is not published to mavenCentral

2025-05-02 Thread James Daugherty
I would like to see us try to exclude repo.grails.org/grails/core from our default applications if at all possible. There are several reasons: 1. The age of that repo: it has so many dependencies in it. 2. It has both snapshot & release artifacts (I realize that the snapshot versions aren't suppo

Re: 'grails-app' folder name

2025-04-18 Thread James Daugherty
The grails-app directory is there to force a division between domain | views | services | assets. It can contain non-source files, and thus it wouldn't make sense to have it under src ever. We need a way to distinguish this, and putting it under resource wouldn't make sense since the files are of

[RESULT][VOTE] Merge Grails-geb & Grails-data-mapping to form a mono repo

2025-04-21 Thread James Daugherty
Hi Everyone, The vote for merging the grails-geb & grails-data-mapping repositories into the grails-core repo[1] has passed. The vote has passed with SIX +1 binding votes. There were TWO +1 non-binding votes. We'll proceed with getting this merged in the coming week. [1] https://lists.apache.o

Re: [RESULT][VOTE] Merge Grails-geb & Grails-data-mapping to form a mono repo

2025-04-21 Thread James Daugherty
processes on your system (or 1, whichever is larger). If we ever get agents with more CPU / memory, we could likely significantly reduce build times. Regards, James On 2025/04/21 15:36:15 James Daugherty wrote: > Hi Everyone, > > The vote for merging the grails-geb & grails-dat

[Weekly Developer Meeting] - 2025-05-07

2025-05-07 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

[Weekly Developer Meeting] - 2025/02/27 - Notes

2025-02-27 Thread James Daugherty
Hi Everyone, We meet every week via a google meeting. Since that meeting does not occur over the dev mailing list, I intend to summarize the results of that meeting going forward to facilitate historical preservation & further discussion. If anyone would like to join this meeting, please let us

M2 ... now M3!

2025-03-03 Thread James Daugherty
Hi Everyone, I started to publish the M2 this morning (as we agreed last week) and realized I kicked off the wrong release task instead of the pre-release task. I've opened https://github.com/grails/grails-core/pull/14049 to prevent this in the future and will start releasing M3 today ... -James

Change Review Proposal

2025-02-27 Thread James Daugherty
Hi Everyone, As part of the weekly meeting, we made an initial attempt at establishing how we will review changes under the ASF. We agreed that these policies should be stored in the `grails-core` project as markdown files. I've tried to translate our initial proposal here: https://github.com/

[Weekly Developer Meeting] - 2025/03/13 - Notes

2025-03-13 Thread James Daugherty
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=MGNnc29hYjFvYW1ndjI5ODJiZXRwZGRjbmMgamFtZXNmcmVkbGV5QHRyaXVtc

Re: [Weekly Developer Meeting] - 2025/02/27 - Notes

2025-03-13 Thread James Daugherty
ce or merge some of the profiles, > and combined with the Application Templates I implemented before, I believe > that it can support more complex configuration and flexible project > skeleton generation. > It's pretty close to the CLI in Ruby on Rails. > > James Daugherty

Re: grails-logging

2025-03-13 Thread James Daugherty
My view is the library provides convention over configuration and should not be removed by default. People always have the option to remove it from their dependency list. We can make it better though: 1. The `log` should support a static context (the ticket Jeff mentioned) 2. Grails should provi

Re: M2 ... now M3!

2025-03-05 Thread James Daugherty
Forge publishes to sdkman, so when it's released it will. I think James F is planning on finishing these other items today. My hope is we can start transferring late today or tomorrow. On Wed, Mar 5, 2025 at 10:40 AM Jeff Brown wrote: > On Wed, Mar 5, 2025 at 9:35 AM James Daugherty

Re: M2 ... now M3!

2025-03-05 Thread James Daugherty
're moving fast! 🚀 😆 > > > > On 2025/03/03 14:03:48 James Daugherty wrote: > > > Hi Everyone, > > > > > > I started to publish the M2 this morning (as we agreed last week) and > > > realized I kicked off the wrong release task instead of the pre-

Re: [DISCUSS] Mailing list selection

2025-02-21 Thread James Daugherty
+1 to proposed users, commits, and notifications mailing lists. On Fri, Feb 21, 2025 at 5:27 AM Søren Berg Glasius wrote: > +1 to proposed users, commits and notifications mailing lists > > I propose that gra...@googlegroups.com should be decommissioned (or made > read only) with a final message

Re: [DISCUSS] Apache Grails Weekly Meeting Day/Time Changes

2025-04-04 Thread James Daugherty
This would be excellent! On Fri, Apr 4, 2025 at 10:46 AM Mattias Reichel wrote: > Works for me! > > Den fre 4 apr. 2025 kl 10:33 skrev Gianluca Sartori : > > > That would be fine for me in CEST > > > > Gianluca Sartori > > > > On Fri, 4 Apr 2025 at 01:29, Walter Duque de Estrada > > wrote: > >

Re: [VOTE] Group Id, Artifact Id rename + Views Gradle Plugins Proposal

2025-03-21 Thread James Daugherty
Michael: can you give a reasons to why you disagree? On Fri, Mar 21, 2025 at 11:00 PM Michael Yan wrote: > [-1],specifically, I disagree with 1, 2, 10 > > On Sat, Mar 22, 2025 at 6:02 AM James Daugherty > wrote: > > > Hi Everyone, > > > > As per the [DISCUS

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-24 Thread James Daugherty
Actually, how about this proposal: Why don't we make anything that is a plugin have a root group id of "org.apache.grails", and anything that's supportive have a nested group name based on the type? On Thu, Mar 20, 2025 at 8:42 AM James Daugherty wrote: > Here are

Re: [DISCUSS] Group Id & Artifact Id Renames

2025-03-29 Thread James Daugherty
, Mar 20, 2025 at 12:58 PM James Daugherty wrote: > @Gianluca, were you ok with the latest draft? > https://github.com/apache/grails-core/pull/14080 > > On Thu, Mar 20, 2025 at 12:56 PM Gianluca Sartori > wrote: > >> Okay sounds good >> >> Gianluca >>

[Weekly Developer Meeting] - 2025/03/27

2025-04-02 Thread James Daugherty
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=MGNnc29hYjFvYW1ndjI5ODJiZXRwZGRjbmMgamFtZXNmcmVkbGV5QHRyaXVtc

[DISCUSS] Grails-cache merger to grails-core

2025-04-02 Thread James Daugherty
Hi Everyone, As we discussed in last week's weekly meeting, we have a desire to merge grails-cache into grails-core. We want to continue to merge repositories to simplify our release strategy and reduce the time to publish artifacts (so we can spend time on developing and not releasing). Recall

Re: [DISCUSS] Grails-cache merger to grails-core

2025-04-03 Thread James Daugherty
lower build times too. -James On Thu, Apr 3, 2025 at 11:37 AM Gianluca Sartori wrote: > +1 > > Gianluca Sartori > -- > Cell. +39 388 1026822 > > > On Wed, 2 Apr 2025 at 19:38, James Daugherty > wrote: > > > Hi Everyone, > > > > As we discussed in

[VOTE] merge grails-cache repository into grails-core

2025-04-03 Thread James Daugherty
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. [] +1 proceed with the proposal [] 0 I don't have a strong opinion about this, but

Re: [DISCUSS] Grails-cache merger to grails-core

2025-04-03 Thread James Daugherty
would help the project, although I know that Gradle build times will > > suffer. > > > > Den tors. 3. apr. 2025 kl. 14.33 skrev David Estes >: > > > > > I agree +1 we should do this! > > > > > > > On Apr 2, 2025, at 11:51 PM, James Daugherty &l

Re: Follow up on H2

2025-05-11 Thread James Daugherty
We publish the tck for others to implement. By default test sources aren’t published, and gradle’s junit runner is designed so that it won’t run tests in a jar. Take a look at the tck config gradle to see how it injects the tests. On Sun, May 11, 2025 at 8:14 PM Walter Duque de Estrada wrote:

Grails Hibernate 6 Branch

2025-05-11 Thread James Daugherty
Hi Everyone, As discussed, I looked at merging the hibernate 6 repository into grails-core. The merged branch is located here: https://github.com/apache/grails-core/tree/merge-hibernate6 A couple notes about this branch: 1. The hibernate6 repo only had material changes to core & docs. I've only

Re: [DISCUSS] Base Grails 7.0.x on Spring Boot 3.5.x

2025-05-08 Thread James Daugherty
Agreed +1 On Thu, May 8, 2025 at 5:27 AM Mattias Reichel wrote: > Yes, we should update! +1 > > Den tors 8 maj 2025 kl 09:22 skrev Søren Berg Glasius : > > > I think this is a good, and responsible idea, especially with all the > tests > > passing. > > > > Den tors. 8. maj 2025 kl. 00.06 skrev J

Re: [DISCUSS] grails-forge publishing requirements

2025-05-09 Thread James Daugherty
d has had substantially more effort applied in recent years. My > opinion is that profiles should exist for Grails 7.0.x, but likely be > deprecated for 7.1.x and then profiles should fold into grails-forge-core > for Grails 8.x.x. As part of this, we need to make it easier to extend >

Re: [DRAFT] Apache Groovy Board Report May 2025 (reporting on Feb/Mar/Apr)

2025-05-13 Thread James Daugherty
Seems like the weekly meetings are ancillary since we summarize them on the mailing list. I'd personally leave it off. Otherwise, It looks fine to me and the point about communication is probably relevant to include. -James On Tue, May 13, 2025 at 4:11 AM Paul King wrote: > I'll add in the 2

Re: H2 error

2025-05-11 Thread James Daugherty
One benefit of H2 is that it is very good at impersonating multiple databases. We haven’t seen these errors previously. What test is this occurring in? I assume by reals you mean a Double is being used? Why is a numeric not being used? On Sun, May 11, 2025 at 8:02 PM Walter Duque de Estrada

Re: Grails Hibernate 6 Branch

2025-05-14 Thread James Daugherty
ks > > > Walter Duque de Estrada > > > On May 11, 2025, at 6:41 PM, Walter Duque de Estrada > wrote: > > > > Agreed on working from this branch. > > > > Thanks for all the work > > > > Walter > > > >> On May 11, 2025, at 4:3

Re: [DISCUSS] grails-forge publishing requirements

2025-05-14 Thread James Daugherty
hing... > > Gianluca Sartori > -- > https://dueuno.com > > On Fri, 9 May 2025 at 16:09, James Daugherty > wrote: > > > > Unfortunately since we still ship shell, we have to do something here. > My > > proposal is how we can move forward with integrating bo

[DISCUSS] Apache Grails 7.0.0-M4

2025-05-17 Thread James Daugherty
Hi Everyone, In the weekly meeting we briefly discussed the outstanding items to release the first Apache milestone: https://lists.apache.org/thread/hm3v6ooqqchms81tljk8h2vpvtj1qfcf I think this discussion merits its own mailing list thread and I'm interested to hear everyone's thoughts on the cu

Re: [DISCUSS] Apache Grails 7.0.0-M4

2025-05-17 Thread James Daugherty
the > initial full release; I'm hoping this can get slated into a release > candidate ahead of GA. > > -Andrew > > On Sat, May 17, 2025 at 2:58 PM James Daugherty > wrote: > > > Hi Everyone, > > > > In the weekly meeting we briefly discusse

[Weekly Developer Meeting] - 2025-05-14

2025-05-15 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

Testing Staging Releases Today

2025-05-23 Thread James Daugherty
Hi Everyone, I'll be testing staging a release today across grails-core & grails-forge. As part of this, you will see a pre-release & tag get created in GitHub. Please note that this will be removed after testing is complete. I'm working on the process to stage a vote so we can hold a vote for th

Re: [DISCUSS] Apache Grails 7.0.0-M4

2025-06-01 Thread James Daugherty
r "some other outstanding item", I do not believe we need to use > 'Apache Grails' in each location that currently says 'Grails'. See Groovy > Documentation: https://groovy-lang.org/single-page-documentation.html. > That saves us some time. > > https://g

Re: Hold off on Running CI in grails-core

2025-06-01 Thread James Daugherty
Hi Everyone, I've placed the 7.0.x branches on grails-core & grails-forge back to 7.0.0-SNAPSHOT so testing can resume. Please see my other thread on the possibility of a 7.0.0-M4 release. Regards, James On 2025/05/29 05:19:09 James Daugherty wrote: > Hi Everyone, > >

Hold off on Running CI in grails-core

2025-05-28 Thread James Daugherty
Hi Everyone, Please hold off on running the CI workflow on grails-core 7.0.x branch. Right now that branch has the 7.0.0-M4 version as part of my stage testing and running that workflow could result in publishing the wrong version to a snapshot repo. I've opened https://issues.apache.org/jira/bro

Re: [DISCUSS] Apache Grails 7.0.0-M4

2025-06-02 Thread James Daugherty
Thanks everyone. Based on this feedback + the PR feedback for the next steps, I'll start this process and open a vote thread soon. On Mon, Jun 2, 2025 at 12:20 PM Søren Berg Glasius wrote: > @James Daugherty With all the work you have > been and are doing, I am confident that we

[VOTE] Release Apache Grails (incubating) 7.0.0-M4

2025-06-02 Thread James Daugherty
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 release can be found on the GitHub pre-release & in the discussion thread at: https://lists.apache.org/thread/3tq

[Weekly Developer Meeting] - 2025-05-28

2025-06-02 Thread James Daugherty
We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.go

Re: [VOTE] Redirect https://grails.org/ to https://grails.apache.org/

2025-06-20 Thread James Daugherty
+1 (binding) On Fri, Jun 20, 2025 at 11:59 AM Gianluca Sartori wrote: > +1 > > Gianluca Sartori > -- > https://dueuno.com > > On Fri, 20 Jun 2025 at 17:56, James Fredley > wrote: > > > > Hi Everyone, > > > > With the https://grails.apache.org/ site published, I believe we are now > > ready to r

  1   2   >