Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate Cookiecutter vs Custom CLI Tool for Project Scaffolding #9

Closed
DanielOber opened this issue Jul 12, 2024 · 3 comments
Closed
Assignees
Labels
Priority: Critical The issue contains work that needs to be done ASAP. Type: Feature The issue is an feature

Comments

@DanielOber
Copy link
Contributor

DanielOber commented Jul 12, 2024

As we prepare to start new projects, we need to determine the best way to scaffold them. We are considering using either Cookiecutter or developing a custom CLI tool.

We need to evaluate and recommend the better option for our specific needs. The preferred choice is cookiecutter, because we dont need to develop a custom solution and dont need to maintain it.

The Scope of this issue is evaluate if cookiecutter fits our needs or if a custom solution is needed.

@devtobi devtobi added Type: Question Priority: Critical The issue contains work that needs to be done ASAP. and removed enhancement labels Jul 19, 2024
@devtobi
Copy link
Member

devtobi commented Jul 26, 2024

POC Idea for CLI-Script:
Input the project name -> Change folder names accordingly, package names, pom.xml, package.json

@devtobi devtobi moved this from Open to Accepted in it@M RefArch Templates Jul 26, 2024
@devtobi devtobi added Type: Feature The issue is an feature and removed Type: Question labels Jul 26, 2024
@DanielOber DanielOber moved this from Accepted to In Progress in it@M RefArch Templates Aug 5, 2024
@DanielOber DanielOber self-assigned this Aug 5, 2024
@devtobi
Copy link
Member

devtobi commented Aug 22, 2024

Will be further handled in it-at-m/refarch#88

@devtobi
Copy link
Member

devtobi commented Aug 22, 2024

Closing

@devtobi devtobi closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in it@M RefArch Templates Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Critical The issue contains work that needs to be done ASAP. Type: Feature The issue is an feature
Projects
Archived in project
Development

No branches or pull requests

2 participants