@@ -74,6 +74,19 @@ Have a look at the `net.sourceforge.pmd.eclipse.p2updatesite` module, there you
7474* the ant script ` packaging-p2composite.ant ` which is used to modify the metadata of the
7575 p2 repo locally before uploading
7676
77+ The release happens in two phases:
78+
79+ 1 . Update the repository locally to prepare the new version:
80+ * Update the changelog
81+ * Update the versions
82+ * Create a tag
83+ * Update the changelog for the next version
84+ * Update the versions
85+ 2 . Push the changes and the tag. The [ travis build] ( https://travis-ci.org/pmd/pmd-eclipse-plugin ) will
86+ then publish the new version on [ bintray] ( https://dl.bintray.com/pmd/pmd-eclipse-plugin/ ) and
87+ [ github releases] ( https://github.com/pmd/pmd-eclipse-plugin/releases )
88+
89+
7790#### Script
7891
7992 # Pick a release BUILDQUALIFIER (e.g. v20170401-0001) and update versions
@@ -126,12 +139,6 @@ Have a look at the `net.sourceforge.pmd.eclipse.p2updatesite` module, there you
126139
127140 echo
128141 echo "Publishing now..."
129- echo "Make sure, you have properties bintray.user and bintray.apikey set in ~/.m2/settings.xml..."
130- mvn clean install -Prelease-composite
131- echo
132-
133- echo
134- echo "Pushing"
135142 git checkout master
136143 git branch -D pmd-eclipse-plugin-rb-$VERSION
137144 git push origin master
@@ -140,7 +147,8 @@ Have a look at the `net.sourceforge.pmd.eclipse.p2updatesite` module, there you
140147 echo Done.
141148
142149Also, don't forget to create a [ News] ( https://sourceforge.net/p/pmd/news/ ) and
143- upload the zipped update site to [ GitHub Releases] ( https://github.com/pmd/pmd-eclipse-plugin/releases ) .
150+ verify, that the zipped update site has been uploaded to
151+ [ GitHub Releases] ( https://github.com/pmd/pmd-eclipse-plugin/releases ) .
144152
145153You can use the following template:
146154
0 commit comments