-
Notifications
You must be signed in to change notification settings - Fork 0
#12 - add a flatten pom step to fix published pom.xml #13
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
Conversation
sbernard31
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I get which artefacts are deployed but ideally the root module proxy-socket-java should not.
sbernard31
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sounds good.
(Just I don't like so much that files generated at build time are not in target repository : I talk about .flattened-pom.xml but this is not a blocking issue)
added forgotten "flattening" step of https://maven.apache.org/guides/mini/guide-maven-ci-friendly.html
Also fixed the release action to download the whole repository to have the tags, however maybe
fetch-deps: 1+fetch-tags: truewould be good also, created #14 for this.