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
If you want to merge the two, I suggest that you refer to the gradle
subcommand in the Grails Shell (implemented by GradleCommand.groovy),
you can wrap the Java API of Grails Forge to implement a subcommand forge,
or like spring.groovy script command in the base profile.
so there are two ways to c
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
As many of you know, the old "Grails Shell CLI" (the grails executable
distributed with SDKMAN up to Grails 5, also runnable via ./grailsw) has
been restored in Grails 7. Meanwhile, the "Grails Forge CLI" (introduced
and distributed via SDKMAN for Grails 6, and powering start.grails.org)
remains th
Recently, I have implemented that the templates in the profiles can support
the Groovy Template Engine, which can reduce 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
ske
