Arch Linux User Repository

This package uses releases from https://marketplace.atlassian.com/plugins/atlassian-plugin-sdk-tgz/versions . Please check there first if a new version is available before flagging the package. Thank you!

@z3ntu. Changed to java-environment.

Btw I've been using this with openjdk for quite some time and it works fine so the dependency can probably be replaced with "java-environment"

This package uses releases from https://marketplace.atlassian.com/plugins/atlassian-plugin-sdk-tgz/versions . Please check there first if a new version is available before flagging the package. Thank you!

What's the purpose of this line?
# add sun jasva path settings to atlas files
find opt/atlassian/plugin-sdk -type f -executable -exec sed -ie 's/# Execute Maven #/# Execute Maven #\nsource \/opt\/java7\/etc\/profile.d\/jdk.sh/g' {} \;

I don't have /opt/java7/etc/profile.d/jdk.sh on my system after installing jdk7 (and running `archlinux-java set java-7-jdk` and `archlinux-java fix`). All atlas-* scripts fail with:
/opt/atlassian/plugin-sdk/bin/atlas-run-standalone: line 164: /opt/java7/etc/profile.d/jdk.sh: No such file or directory

Removing the line fixes the issue, and the scripts seem to run as expected.

The comment mentions sun java; perhaps this is a legacy thing that's no longer needed?

Please don't flag this package all the time.

I know there are some newer releases from Atlassian but neither of them is the official latest version, see https://marketplace.atlassian.com/plugins/atlassian-plugin-sdk-tgz/versions

Thank you!

I don't think that relying on JAVA_HOME is a good option.

The Atlassian products definitely needs an oracle JDK and 1.7 is the only version that is suitable for all products right now. Maybe we might switch to 1.8 in a couple of weeks.

I have openjdk 8 as default java but that as stated above this not an option for the Atlassian plugin sdk. jdk7 is a dependency and if you install the jdk7 package from AUR you won't have any errors.

The lines in the PKGBUILD that add in a profile source for jdk7 are no longer required, and just cause an error to show up every time any of the commands that run Maven are run, as the point to a nonexistant file.

I suggest that they get removed, and just rely on JAVA_HOME like normal.

jdk7-compat is now called jdk7.

Please update dependency list according to the request [1]:

jdk7-compat -> jdk7

1. https://mailman.archlinux.org/pipermail/aur-requests/2014-September/001431.html

Atlassian just released SDK version 5.0:

https://developer.atlassian.com/display/DOCS/AMPS+SDK+5.0.0+Release+Notes

Most important change: They now use Maven v3.2.1!