-
Notifications
You must be signed in to change notification settings - Fork 27
/
release-howto.txt
34 lines (25 loc) · 1.35 KB
/
release-howto.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
Performing a release to Maven and Openshift involves the following steps
Publish to Maven Central
Add Sonatype password to server ossrh in local settings.xml
<settings>
<servers>
<server>
<id>ossrh</id>
<username>XXX</username>
<password>XXX</password>
</server>
</servers>
</settings>
Release to Sonatype with Github password and gpg passphrase:
mvn release:prepare release:perform [email protected] -Dpassword=XXX -Darguments="-Dgpg.passphrase=XXX"
The above command should automatically release from staging repo https://oss.sonatype.org/
Details:
http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
In case that signing failed and the build asks for the gpg passphrase over and over again, perform the release once more:
mvn release:perform -Darguments="-Dgpg.passphrase=XXX"
Publish to Openshift
Check that new hydra-java release has become available in Central:
http://search.maven.org/#search%7Cga%7C1%7Chydra-service
Adjust latest version in openshift project: ssh://[email protected]/~/git/jbosswildfly.git/
Run deployment build (if necessary; runs automatically every hour): https://jenkins-escalon.rhcloud.com/job/jbosswildfly-build/
The openshift project has its own web.xml, configuration changes must be applied there, too.