Package Details: atlassian-plugin-sdk 6.2.6-1

Git Clone URL: https://aur.archlinux.org/atlassian-plugin-sdk.git (read-only)
Package Base: atlassian-plugin-sdk
Description: Atlassian plugin software developer kit
Upstream URL: https://marketplace.atlassian.com/plugins/atlassian-plugin-sdk-tgz
Licenses: Apache License 2.0
Submitter: lepokle
Maintainer: lepokle
Last Packager: lepokle
Votes: 4
Popularity: 0.000000
First Submitted: 2011-02-05 09:49
Last Updated: 2016-06-05 07:45

Latest Comments

catharsis commented on 2015-04-10 07:23

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?

lepokle commented on 2015-04-06 20:57

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!

lepokle commented on 2015-04-06 06:25

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.

Phreakazoid commented on 2015-04-02 04:15

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.

kungfoo commented on 2015-02-11 16:03

jdk7-compat is now called jdk7.

arcanis commented on 2014-09-06 21:55

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

jdk7-compat -> jdk7

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

mrueegg commented on 2014-06-04 15:21

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!

Lykathia commented on 2014-01-01 19:07

New version: 4.2.10
pkgver=4.2.10
md5sums=('636f26607dccb3b03fa3b3409c399d8e')

joschi commented on 2013-09-08 11:07

Updated PKGBUILD for atlassian-plugin-sdk 4.2.9: https://github.com/joschi/AUR/blob/9897ca4f87a5c65ad133e13d98bc403439684dab/atlassian-plugin-sdk/PKGBUILD

joschi commented on 2013-08-12 20:20

Would it be possible to depend on java-environment rather than sun-java6? I know that the SDK documentation says it required Sun JDK 6 but it also works with OpenJDK 7 (or almost any other Java 6 compatible JDK) out of the box.

Proposed PKGBUILD at https://github.com/joschi/AUR/blob/09e33df690ce2631a2c8cce520f617f273ecc511/atlassian-plugin-sdk/PKGBUILD

All comments