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

[REQUEST] Automatically append version number to JAR releases #52

Closed
barbeau opened this issue Mar 11, 2020 · 0 comments · Fixed by #108
Closed

[REQUEST] Automatically append version number to JAR releases #52

barbeau opened this issue Mar 11, 2020 · 0 comments · Fixed by #108

Comments

@barbeau
Copy link
Member

barbeau commented Mar 11, 2020

Is your feature request related to a problem? Please describe.
When downloading a release like https://github.com/MobilityData/gtfs-validator/releases/tag/v1.0.0, it's not clear after download which version I downloaded. It's easy to mix up different versions of the file because they all have the same file name - gtfs-validator.jar.

Describe the solution you'd like
Automatically append the version number to the end of the JAR file name to make it clearer which version a particular JAR file is.

So, the new release file name for v1.0.0 would be:

gtfs-validator-v1.0.0.jar

I've done this before using Gradle on Android projects, like https://github.com/OneBusAway/onebusaway-android/blob/master/onebusaway-android/build.gradle#L346:

        android.applicationVariants.all { variant ->
            if (variant.buildType.name == "release") {
                variant.outputs.all { output ->
                    outputFileName = "${variant.name}-v${variant.versionName}.apk"
                }
            }
        }

But I've never configured this on a desktop Java Gradle project before.

I know normally on a Maven project when you do a release it automatically appends the version number to the file name.

Describe alternatives you've considered
No action - leave the release file name as-is

Additional context
None

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.

1 participant