Arch Linux User Repository

Separate Community Edition and Ultimate Edition versions seem to be going away as of 2025.3, per https://blog.jetbrains.com/idea/2025/07/intellij-idea-unified-distribution-plan/ :

With the 2025.3 release, IntelliJ IDEA Community Edition will no longer be distributed as a separate product. Instead, all users will download a single IntelliJ IDEA distribution: one installer and one update stream.

If you are currently using Community Edition, your IDE will automatically update to the unified distribution via the usual patch update process. You will get access to additional features at no cost and a more seamless experience. You will also be able to try Ultimate features with just one click.

The change is minimal for Ultimate users: the IDE will simply be called IntelliJ IDEA without the “Ultimate” suffix.

EDIT:

Their FAQ mentions more about open-source versions:

Can I still build an open-source version of IntelliJ IDEA?

The source code remains on GitHub, and we are fully committed to maintaining it. In addition, we will publish open-source builds to GitHub Releases and provide ready-to-use CI/CD pipelines powered by GitHub Actions, reinforcing our commitment to transparency and productive open-source collaboration.

they keep changing that depending on who's releasing

It appears intellij has changed their tar url format with 2025.2, now using buildver instead of the IDE version.

New version of EAP is available: https://youtrack.jetbrains.com/articles/IDEA-A-2100662348/IntelliJ-IDEA-2025.1-EAP-1-251.14649.49-build-Release-Notes

and today, it seems the old 2014 version has been released, any chance to release a new EAP version?

Version Expired

I know, but it is not clear that the package is bundled with jre (like with any other package). Also, I need to disable bundled jre sometimes in case of problems.

You do not need to maintain a separate package actually. That will be a "split" package. I.e. in one PKGBUILD the two packages are built. See an example in webstorm-eap.

@ashark no I like keeping them same per release. Each of them has different versions of JBR anyway

@artafinde Can you please separate the bundled jre to a separate package? See webstorm-eap as an example.

added aarch64 support after jetbrains released builds for aarch64 on linux

diff --git a/PKGBUILD b/PKGBUILD
index 916bc83..3158e09 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -15,10 +15,19 @@ url="http://www.jetbrains.com/idea/nextversion"
 license=('custom')
 depends=('java-environment' 'giflib' 'libxtst' 'libdbusmenu-glib')
 _archive="ideaIU-${_buildver}.tar.gz"
-source=("https://download.jetbrains.com/idea/${_archive}"
-        "intellij-idea-ue-eap.desktop")
-sha256sums=($(curl -s "https://download.jetbrains.com/idea/${_archive}.sha256" | cut -f1 -d" ")
-            'af5a9e49b921dbdc5b960dedc27e15b2510896ff6e58d983fca7de6a6fd18f38')
+_archive_aarch64="ideaIU-${_buildver}-aarch64.tar.gz"
+# downloads aarch64 version if arch matches
+if [ "${CARCH}" == "aarch64" ]; then
+    source=("https://download.jetbrains.com/idea/${_archive_aarch64}"
+    "${pkgname}.desktop")
+    sha256sums=($(curl -s "https://download.jetbrains.com/idea/${_archive_aarch64}.sha256" | cut -f1 -d" ")
+    'af5a9e49b921dbdc5b960dedc27e15b2510896ff6e58d983fca7de6a6fd18f38')
+else
+    source=("https://download.jetbrains.com/idea/${_archive}"
+    "${pkgname}.desktop")
+    sha256sums=($(curl -s "https://download.jetbrains.com/idea/${_archive}.sha256" | cut -f1 -d" ")
+    'af5a9e49b921dbdc5b960dedc27e15b2510896ff6e58d983fca7de6a6fd18f38')
+fi
+
 package() {
     install -dm755 "${pkgdir}/opt/${pkgname}"
     cp -r --no-preserve='ownership' "${srcdir}/${_pkgname}-${_buildver}/"* "${pkgdir}/opt/${pkgname}"

Just helped a friend with some confusing behavior around starting this from terminal.

It seems you've made a slight error in the last "ls -s" command. Since it links to ${pkgdir} it links to the folder in which the package is being build, making it link to nothing when that folder is cleaned away. This is ok with other commands, but since "ln -s" just saves down the lefthand path as is upon execution this ends up behaving unexpectedly.

Dropping the ${pkgdir} entirely on that line should resolve it fully.