Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Configuring settings.xml file

To stage release, you we'll need to enable connection with Sonatype OSSRH

...

Code Block
titlesettings.xml
<settings>
	...
	<servers>
		<server>
			<id>sonatype-nexus-staging</id>	
			<username>your-jira-id</username>
			<password>your-jira-pwd</password>
		</server>
	</servers>
 
	...
</settings>

In case you don't already have Sonatype JIRA account and publish rights to Slice, firstly you'll need to create an account on https://issues.sonatype.org/.

After that to get write permission to Slice, you will need to ask for it using comment by creating a JIRA ticket (you can take a looks at comments on this ticket).

 

The information about public key and scm username are also required and will need to add to chosen profile a path to the public key and scm.username file, e.g.:

Code Block
titlesettings.xml
<settings>
	...
	<profile>
		<id>slice-author</id>
		<activation>
			<activeByDefault>false</activeByDefault>
		</activation>
  
		<properties>
    			<privateKey>C:\Users\kamil.ciecierski\.ssh\id_dsa.pub</privateKey>
    			<scm.username>git</scm.username>
		</properties>
		...
	</profile> 
	...
</settings>  

...

Code Block
languagebash
titleConsole
mvn release:prepare:release

You will be prompted for the version number for each module of the project, tag name, and next SNAPSHOT versions. You will need also type the passphrase for the key, which you generated during Generating a PGP Signatures step. When this command finish successfully, the version section of each module's pom.xml file will be updated.

...