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

Maven POM update towards 2.0 #162

Merged
merged 3 commits into from
Dec 11, 2016
Merged

Conversation

oleg-nenashev
Copy link
Member

Add support of Maven releases for the 2.0 release

  • - Use GitHub Releases as a source of the binary file (yes, you do not need Windows to release to Maven anymore)
  • - Enhance the POM.xml description
  • - Add verification of POM/WinSW consistency during the release

Fixes #80

@oleg-nenashev oleg-nenashev added this to the winsw-2.0 milestone Dec 10, 2016
@oleg-nenashev
Copy link
Member Author

@reviewbybees

@ghost
Copy link

ghost commented Dec 10, 2016

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@recena
Copy link

recena commented Dec 11, 2016

🐝

@oleg-nenashev
Copy link
Member Author

@reviewbybees done

@oleg-nenashev oleg-nenashev merged commit 98f32e1 into winsw:master Dec 11, 2016
oleg-nenashev added a commit that referenced this pull request Dec 20, 2016
@nxtn nxtn modified the milestones: winsw-2.0, 2.0.1, 2.0.0 Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maven Build flow should pick releases from GitHub or NuGet
3 participants