Make profiles optional for the Grails-Shell CLI
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
Attempt to make profile optional for the Grails-Shell CLI.
grails-forge-cli is the modern way to generate Grails applications. Generating applications with grails-shell-cli and profiles was brought back to support a more gradual transition.
grails-shell-cli does far more than application generation and that other 90% will continue to be important.
Grails-Shell CLI can be updated to execute Application Commands without profiles, so that profiles are only used for for the create-* commands.
Profiles are now a redundant burden that is difficult to keep
up to date and consistent with Forge, because they use total different
technology. If Forge and Shell can support same template engine and share
the same skeleton templates to generate the projects, so we can provide
both of them.
Migrate Groovy script commands from profiles to grails-shell-cli so they can be used without the Profile.
Use Groovy Templates as the command templates.
https://github.com/apache/grails-core/issues/14699
Contributor guide
Research direction
Start by reviewing the grails-shell-cli Application Commands and the existing create-* commands that use profiles. Trace the Groovy script commands and assess how Groovy Templates could replace profile-based command templates. Done means non-create commands run without profiles while create-* commands retain the required generation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100