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 distributions for both maven 3.9.x and 4.0.x #796

Merged
merged 1 commit into from
Mar 7, 2023

Conversation

gnodet
Copy link
Contributor

@gnodet gnodet commented Feb 17, 2023

No description provided.

@gnodet gnodet marked this pull request as ready for review February 17, 2023 14:13
@gnodet gnodet added this to the 1.0.0-m2 milestone Mar 7, 2023
@gnodet gnodet modified the milestones: 1.0.0-m2, 1.0.0-m5 Mar 7, 2023
@gnodet gnodet merged commit 95b40a3 into apache:master Mar 7, 2023
executable="**/bin/mvnd"/>

<archive name="maven-${project.version}-mvnd-mvn39-${os.detected.name}-${os.detected.arch}.tar.gz"
executable="**/bin/mvnd"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just thinking out loud - this produces a file named e.g. maven-1.0.0-m5-SNAPSHOT-mvnd-mvn39-linux-amd64.tar.gz which to me sounds like this is somewhat related to Maven version 1.0.0-m5-SNAPSHOT, which is not really the case. This is the version of the Maven daemon. Was there a specific reason to change the naming scheme compared to the older branches (e.g. maven-mvnd-0.10.0-SNAPSHOT-linux-amd64.tar.gz)? Would it make sense to go back to maven-mvnd-1.0.0-m5-SNAPSHOT-mvn39-linux-amd64.tar.gz?

@gnodet gnodet deleted the v39+v40 branch October 26, 2023 05:20
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 this pull request may close these issues.

2 participants