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

Provide option to create JReleaser configuration #9

Open
gunnarmorling opened this issue Nov 14, 2021 · 4 comments · May be fixed by #22
Open

Provide option to create JReleaser configuration #9

gunnarmorling opened this issue Nov 14, 2021 · 4 comments · May be fixed by #22

Comments

@gunnarmorling
Copy link
Member

I'm not sure whether we always should create that by default, but it may be an opt-in feature which can be chosen when creating a project from the archetype. WDYT, @aalmiray?

@aalmiray
Copy link
Contributor

Well, I think archetypes cannot modify the contents of the pom.xml unless we add a post processing Groovy script. Are you up to that? 😼

@gunnarmorling
Copy link
Member Author

Yes, I think there will be no way around that. A few of the customizations will require it in all likelihood, e.g. adjusting license headers in the generated files as per the selected license (see #2).

@gunnarmorling
Copy link
Member Author

Hey @aalmiray, so with the basic archetype in place, do you think you could give it a shot to update the template to include all the required configuration for releasing to Maven Central? I can take care of archetype-izing it then, if needed. WDYT?

@aalmiray
Copy link
Contributor

aalmiray commented Dec 4, 2021

OK, I'll see what I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants