Package Details: intellij-idea-ultimate-edition 2025.1-1

Git Clone URL: https://aur.archlinux.org/intellij-idea-ultimate-edition.git (read-only, click to copy)
Package Base: intellij-idea-ultimate-edition
Description: An intelligent IDE for Java, Groovy and other programming languages with advanced refactoring features intensely focused on developer productivity.
Upstream URL: https://www.jetbrains.com/idea/
Licenses: custom:commercial
Conflicts: intellij-idea-ultimate-edition-jre
Provides: intellij-idea-ultimate-edition-jre
Submitter: uwolfer
Maintainer: uwolfer (dcelasun)
Last Packager: dcelasun
Votes: 427
Popularity: 3.31
First Submitted: 2009-10-28 09:09 (UTC)
Last Updated: 2025-04-16 15:17 (UTC)

Dependencies (6)

Required by (5)

Sources (5)

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 43 Next › Last »

<deleted-account> commented on 2016-09-11 12:12 (UTC)

What can be done with "inline" updates, I mean patches from GUI? It is a bit uncomfortable to download and untar the whole 800 MB package every time.

uwolfer commented on 2016-07-13 05:49 (UTC)

@jshap70: Do you think downloading the checksum from the same source as you retrieve the download is really safe? If you have write access, you can manipulate both source and checksum. I will look into the JRE bundling later. I don't really like the idea of having a bundled JRE, but it seems that JetBrains is "forced" to do that...

jshap commented on 2016-07-12 22:51 (UTC) (edited on 2016-07-12 23:59 (UTC) by jshap)

bumping @Teedee 's comment about including the JRE. Also, take a look at https://aur.archlinux.org/packages/intellij-idea-ue-eap/ 's pkgbuild to automatically get sha256 sums from jetbrains. You just add .sha256 onto the end of the .tar.gz url.

<deleted-account> commented on 2016-07-11 21:03 (UTC)

The new font ligatures feature in the upcoming release relies on the bundled Jetbrains JRE. It seems more of a hassle to change the pkgbuild to download the release with the bundled Jetbrains JRE (also have to deal with checksums etc) than to just have a commented line in the pkgbuild which removes the bundled JRE after download. I suggest switching back to the download with the Jetbrains JRE bundled.

<deleted-account> commented on 2016-06-14 11:01 (UTC)

Removing the epoch again now confused pacman again: warning: downgrading package intellij-idea-ultimate-edition (2:2016.1.2b-1 => 2016.1.3-1) I think now that it was there once, we need to keep it.

voop commented on 2016-06-06 16:04 (UTC)

@rdoursenaud I don't think epoch version bumping is necessary. It also doesn't make sense bump epoch number when minor change is released. I would rather use version 2016.1.2.b-1, which will not produce "downgrade warning issue" mentioned in previous comments. I would also consider compatibility fix from openssl package to avoid having two version numbers in PKGBUILD: {code} _ver=1.0.2h # use a pacman compatible version scheme pkgver=${_ver/[a-z]/.${_ver//[0-9.]/}} {code}

rdoursenaud commented on 2016-06-02 02:31 (UTC)

That's exactly why there is epoch in PKGBUILD. See: https://wiki.archlinux.org/index.php/PKGBUILD#epoch Also according to the wiki, you can use vercmp to make sure the version is seen as newer.

Chewtoy commented on 2016-06-01 05:23 (UTC)

@uwolfer & @blmarket: Yes. Exactly. Pacman thinks the "b" means that the package is a beta-version. And since the last package wasn't a "b" version, this 'must' be a downgrade. However, if you go to jetbrains download page ( https://www.jetbrains.com/idea/download/download-thanks.html?platform=linux ), they serve the "b"-version as the latest one. So I suppose this thing is more of a "Who the heck uses letters in stable releases?" and "Who the heck adds letters to the next iteration of a stable release without bumping the numbers?" (to which the answer seems to include JetBrains)

blmarket commented on 2016-06-01 01:49 (UTC)

pacman thinks 2016.1.2-1 is the newer than 2016.1.2b-1, maybe it regards 'b' as beta? warning: downgrading package intellij-idea-ultimate-edition (2016.1.2-1 => 2016.1.2b-1)