Redemption of Atlassian Answers T-Shirts, Backpacks and Jackets is temporarily unavailable while we migrate to a new third-party provider for https://swag.atlassian.com.
I think there are really good tutorials on how to use the Plugin SDK, how to create the plugin skeleton etc. There are also some good guildelines (well, currently already obsolete, but still nice) what is the process needed for applying a plugin for plugin exchange, but towards its end I miss a step-by-step guides especially about releasing of the plugin.
What I miss though (couln't find it) is a step by step instructions how to use atlas-release command. I also got some very confusing information about the contrib maven repository. I don't know now - is it mandatory to have an account there or not?
My plugin will be hosted on bitbucket and I would be very grateful for simple instructions: what to put in my pom.xml when I want to release my plugin? What should be the <scm> configuration for git on bitbucket, what should be my <repositories> in pom.xml.
Also, would be useful to explain shortly for example, how to use I guess atlas-mvn to build javadocs or sources.
Yes, I am a newbie in maven who knows Java in general and so far I was able to follow the available instructions, but now I am stuck with not knowing how to release the thing. I am afraid of running the maven release commands just to try things because I know it can cause some sideeffect to my local repo which are maybe hard to rollback (for a newbie).
Any help greatly appreciated!
I can give you a part of the answer, but some people are more relevant about the Maven Release plugin and the way the Atlassian Contrib repo is managed. There is a page on DAC about the Atlassian Repositories and how to declare them in your pom.xml.
If you look at the source code of AMPS (ReleaseMojo), it is just calling mvn release:prepare and mvn release:perform, so I suggest you call these commands directly, and get information on the website of maven-release-plugin about the details. There is a guide to releasing on the plugin's website. Note that old versions had an issue with Git, so check you're using the very last one.
Imagine you're developing THING 1.0-SNAPSHOT. In git, your pom.xml reads "<version>1.0-SNAPSHOT</version>" while you develop, then you want to deliver 1.0. You will keep developing version 2, so the new version will be 2.0-SNAPSHOT.
Here is an example of SCM tag for gitbucket:
Best of luck,