HTTPS SSH

Atlassian Platform POMs

Usage

In your project's parent pom, import via dependency management:

<properties>
    <platform.version>2.22.7</platform.version>
</properties>

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.atlassian.platform</groupId>
            <artifactId>platform</artifactId>
            <version>${platform.version}</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
        <dependency>
            <groupId>com.atlassian.platform</groupId>
            <artifactId>third-party</artifactId>
            <version>${platform.version}</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

In your modules, import the desired dependencies with a scope, but not a version e.g.

<dependencies>
    <dependency>
        <groupId>com.atlassian.sal</groupId>
        <artifactId>sal-api</artifactId>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>org.hamcrest</groupId>
        <artifactId>hamcrest-library</artifactId>
        <scope>test</scope>
    </dependency>
</dependencies>

Atlassian Developer?

Committing Guidelines

Upon release of a new version of a Platform Module (go/platform), please push the version to the appropriate branch. No PR is required.

Please discuss with the Armata team about which branch to push to, see Platform Rules Of Engagement (go/proe).

Builds

The Bamboo builds for this project are on EcoBAC

Releasing

Releasing is done with a release stage in the bamboo CI build. See the Platform Rules Of Engagement for details.

Notes On Version 4.0

Platform version 4.0.0 and 4.0.1 were experimental builds of the platform containing Velocity 1.7 capable modules. There are no plans to adopt these modules, so the branch has been renamed to 4.0.x-dead. These changes are not present in master.

External User?

Issues

Please raise any issues you find with this module in JIRA