To release the rsp-server, a few steps are required, with verification at each step.
Run the following command to publish
$ mvn clean deploy
The above command should cause a new staging repository to be formed. Go to https://repository.jboss.org/nexus/ to begin browsing for it. Then, on the left, click staging repositories. Sort by updated to find the correct repository. Select that item.
Then, in the bottom view, browse to the content tab. Traverse the tree manually and verify that some (or most) of the expected artifacts exist. Whene verything looks ok, you may close the repository.
If the close fails due to a non-unique item, it is most likely the targetplatforms folder. In that case, you should edit targetplatform/rsp-target.target and change a comment near the end of the file listing the version. And try again.
If everything has worked so far, copy the url for the closed repository.
You can execute the following commands to test.
PLEASE MODIFY THE COMMAND.
The value REPONUM should be replaced with the number of the repository found in nexus.
The value NEWVERSION should be replaced with the new target version that you have just released.
rm -rf ~/.m2/repository/org/jboss/tools/rsp/
git clone [email protected]:robstryker/testRSP.git
cd testRSP/
cat pom.xml | sed 's/profile-14851/profile-REPONUM/g' | sed 's/0.12.1.Final/NEWVERSION/g' > pom2.xml;
mv pom2.xml pom.xml
mvn clean install
If the staging repository looks good, you can click the 'release' button.
Verify that nexus now includes all expected files and versions. https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/rsp/
The 'release' should have dropped the staging repository, so you need to run the following in your testRSP folder once more:
rm -rf ~/.m2/repository/org/jboss/tools/rsp
mvn -U clean install
Verify build is green again.
Finally, to ensure everything was fully released, ensure that the distribution file with the approporiate version exists here