-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Maven Build flow should pick releases from GitHub or NuGet #80
Comments
oleg-nenashev
added a commit
to oleg-nenashev/winsw
that referenced
this issue
Feb 2, 2015
Changes summary: * Add "version" and "help" commands * Return error on the unsupported command * Add CLITestHelper to simplify the testing of the service CLI * Add unit-tests for the new functionality Resolves winsw#78 and winsw#46 Related to winsw#80 Signed-off-by: Oleg Nenashev <o.v.nenashev@gmail.com>
The bug has been fixed in winsw-1.17 |
This was updated for 1.18, however the 1.19 release still misreports 1.18 as the assembly version... |
Fixed in 2.19.1 BTW it's still a risk |
oleg-nenashev
changed the title
WinSW Assembly version differs from pom.xml
POM release should fail if WinSW Assembly version differs from pom.xml
Nov 26, 2016
oleg-nenashev
changed the title
POM release should fail if WinSW Assembly version differs from pom.xml
Maven Build flow should pick releases from GitHub or NuGet
Dec 10, 2016
So the new flow has been merged. Maven release attempts will fail if the version differs from the WinSW release |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A correct Assembly version is required to track dependencies and to show it in CLI.
TODOs:
Required for #78
The text was updated successfully, but these errors were encountered: