What's the proper method to determine the latest version of SAL?

I had been developing a simple plugin against Stash 2.0.3. In order to test it with our running Stash 2.1.2 instance, I changed the stash.version and stash.data.version in the pom.xml from 2.0.3 to 2.1.2. When I execute atlas-run, most dependencies are downloaded, but one fails:

Downloading: https://m2proxy.atlassian.com/repository/public/com/atlassian/sal/sal-api/2.1.2/sal-api-2.1.2.pom
[INFO] Unable to find resource 'com.atlassian.sal:sal-api:pom:2.1.2' in repository atlassian-public (https://m2proxy.atlassian.com/repository/public)

Downloading: http://repo1.maven.org/maven2/com/atlassian/sal/sal-api/2.1.2/sal-api-2.1.2.pom
[INFO] Unable to find resource 'com.atlassian.sal:sal-api:pom:2.1.2' in repository central (http://repo1.maven.org/maven2)

Downloading: https://m2proxy.atlassian.com/repository/public/com/atlassian/sal/sal-api/2.1.2/sal-api-2.1.2.jar
[INFO] Unable to find resource 'com.atlassian.sal:sal-api:jar:2.1.2' in repository atlassian-public (https://m2proxy.atlassian.com/repository/public)

Downloading: http://repo1.maven.org/maven2/com/atlassian/sal/sal-api/2.1.2/sal-api-2.1.2.jar
[INFO] Unable to find resource 'com.atlassian.sal:sal-api:jar:2.1.2' in repository central (http://repo1.maven.org/maven2)

Is there a matching release of SAL for each release of Stash, or should I have the dependency below set to a fixed value?

<dependency>
    <groupId>com.atlassian.sal</groupId>
    <artifactId>sal-api</artifactId>
    <version>${stash.version}</version>
    <scope>provided</scope>
</dependency>

1 answer

1 accepted

1 vote
Jason Hinch Atlassian Team Feb 20, 2013

The best way to ensure you are using the same versions of APIs as Stash is to use a import scope on our parent pom.

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.atlassian.stash</groupId>
            <artifactId>stash-parent</artifactId>
            <version>${stash.version}</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dpendencies>
</dependencyManagement>

You then can omit the version from all the dependencies which Stash provides that you have defined in the dependencies section.

There's a small typo in the above XML, but otherwise, this worked fantastically. Thanks!

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,764 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you