forked from ops4j/org.ops4j.pax.url
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
65 lines (47 loc) · 1.42 KB
/
README
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
h1. Release paxurl
If you have all required rights to release pax-url follow these steps:
1) add this into your ~/.m2/settings.xml and fill in your credentials
and local paths:
{code}
<server>
<id>sonatype.staging.snapshots.deploy</id>
<username>YOURNAME</username>
<password>SECRET</password>
</server>
<server>
<id>sonatype.staging.releases.deploy</id>
<username>YOURNAME</username>
<password>SECRET</password>
</server>
<profile>
<id>release</id>
<properties>
<gpg.passphrase>gpgpassphrase</gpg.passphrase>
<release-paxurl-altGitURL>scm:git:file:///path/to/local/repo/org.ops4j.pax.url</release-paxurl-altGitURL>
</properties>
</profile>
{code}
2) prepare the release:
{code}
mvn -Prelease,repos.sonatype.staging -Darguments="-Prelease,repos.sonatype.staging" release:prepare -DautoVersionSubmodules=true
{code}
3) perform the release (this fails):
{code}
mvn -Prelease,repos.sonatype.staging -Darguments="-Prelease,repos.sonatype.staging" release:perform
.... auth failure in site:deploy ...
{code}
4) go into the checkout directory:
{code}
cd target/checkout
{code}
5) push to oss.sonatype.org:
{code}
mvn -Prelease,repos.sonatype.staging source:jar javadoc:jar deploy
{code}
6) push to github:
{code}
git push
{code}
8) go to oss.sonatype.org and push pax-url to central:
Select Staging Repositories, org.ops4j, Close and finally Release.
The new artifacts will appear on Maven Central within an hour or so.