Deprecate the old grails-shell project

[puneetbehl]

Issue description

Starting Grails 6, we have introduction the new CLI. So, we would need to deprecate the grails-shell subproject or extract it out from grails-core.

[guillermocalvo]

@puneetbehl Grails Profile Gradle Plugin still depends greatly on grails-shell. I tried moving classes under org.grails.cli.profile from grails-shell to grails-gradle-plugin, but those classes depend on other packages that are unrelated to profiles, so I don't think it would be a clean move.

Is Grails Profile Gradle Plugin still relevant? In other words, can we deprecate it along with grails-shell, or do we need to keep maintaining it for the foreseeable future?

[puneetbehl]

Yes, I think it is not used any longer. Since Grails 6, we stopped using/creating Grails profiles. The plugin is used for distribution of Grails Profile. Also, there is GrailsProfilePublishPlugin which may also be removed.

[guillermocalvo]

Yes, I think it is not used any longer. Since Grails 6, we stopped using/creating Grails profiles. The plugin is used for distribution of Grails Profile. Also, there is GrailsProfilePublishPlugin which may also be removed.

Thanks for the info! I created a PR to remove those legacy plugins from grails-gradle-plugin.

I looked into possible Grails projects that may still depend on the deprecated CLI and found several repositories. Most of them seem obsolete, but I'd like to know your opinion before we remove grails-shell from grails-core.

1. grails-profile-repository
   • According to the README file "This repository is no longer used. Profiles now live in https://github.com/grails-profiles".
2. grails-profiles
   • You mentioned that Grails profiles are not used anymore, so I guess we can ignore all repositories under grails-profiles that still depend on grails-shell.
3. grails-wrapper
   • I believe this is just another legacy project that used to depend on grails-shell.
4. legacy-grails-doc
   • Although this repository has recent commits, I think we can ignore it too. I guess there may be some scheduled job that pushes changes periodically.
5. grails-database-migration
   • I'm not so sure about this one. It looks like it's being actively developed but it still depends on grails-shell.

So what do you think about all these legacy repositories @puneetbehl? Would it be possible to archive them in GitHub to make them read-only and indicate that they are no longer maintained?

[puneetbehl]

The legacy-grails-doc is created to surpass GitHub limit for publishing the Grails documentation on gh-pages. So, extracted the older version docs to a different repository.

I am also not so sure about how Grails Database Migration plugin depends on grails-shell. It would be good to investigate the need.

For the rest of these, I believe it is safe to archive them.

[guillermocalvo]

Important

@puneetbehl Please take a look at this PR: grails/grails-database-migration#350