You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
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
The text was updated successfully, but these errors were encountered: