Package Details: eclipse-jee 2:4.24-1

Git Clone URL: https://aur.archlinux.org/eclipse-jee.git (read-only, click to copy)
Package Base: eclipse-jee
Description: Highly extensible IDE (Enterprise Java and Web version)
Upstream URL: https://www.eclipse.org/
Licenses: EPL
Conflicts: eclipse
Provides: eclipse
Submitter: altermetax
Maintainer: altermetax
Last Packager: altermetax
Votes: 6
Popularity: 0.047690
First Submitted: 2021-08-22 12:13 (UTC)
Last Updated: 2022-06-15 15:40 (UTC)

Dependencies (3)

Required by (41)

Sources (2)

Latest Comments

yoghurt114 commented on 2022-07-31 19:37 (UTC)

@M-M I was running into the same issues and indeed downgrading the webkit2gtk package seemed to resolve it. Thanks!

M-M commented on 2022-07-30 20:35 (UTC)

Hello, I was previously using Eclipse 4.23. I updated to 4.24 and eclipse began to crash. I was looking at core dumps and stack traces and noticed mentions of webkit2gtk...particularly libwebkit2gtk-4.0.so.37. I checked if webkit2gtk had been updated and it did - webkit2gtk-2.36.5-1. I downgraded to the last version webkit2gtk was working fine with eclipse, and now eclipse is not crashing. The version I downgraded to was webkit2gtk-2.36.4-2. Was wondering if anyone else having this issue with the latest version of webkit2gtk.

altermetax commented on 2022-04-16 14:41 (UTC)

Does not happen here. Have you tried it on a clean workspace?

archlinuxforever commented on 2022-04-16 07:54 (UTC)

The Version: 2022-03 (4.23.0) Build id: 20220310-1457 returns this error message in the Debugger console tab: "Could not create the view: org.eclipse.cdt.debug.ui.debuggerConsoleView".

And on Executables tab there is another error: "Could not create the view: org.eclipse.cdt.debug.ui.executablesView".

altermetax commented on 2021-12-28 22:22 (UTC) (edited on 2021-12-28 22:22 (UTC) by altermetax)

@AllirionX this happens if you had somehow edited the eclipse.ini file. Run the following command (make sure to backup the existing eclipse.ini if you need it):

sudo mv /usr/lib/eclipse/eclipse.ini.pacnew /usr/lib/eclipse/eclipse.ini

I didn't notice @Musikolo's suggestion, I'll take a look at it and fix this problem when I've got some time.

AllirionX commented on 2021-12-28 22:17 (UTC) (edited on 2021-12-28 22:23 (UTC) by AllirionX)

After installing the latest update of that package, eclipse is not starting with this error: plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.0.v20200915-1442: cannot open shared object file: No such file or directory

This is due to the package versions not being updated in the eclipse.ini file.

Musikolo commented on 2021-09-18 17:13 (UTC) (edited on 2021-09-18 17:13 (UTC) by Musikolo)

Regarding my last request, I found backing up the eclipse.ini file doesn't work the expected way, because it doesn't update some plugin paths the file. You can see what I'm talking about this screenshot.

Just in case it helps, you can look at the workaround I implemented for the spring-tool-suite package I maintain. Admittedly, it isn't the best thing in the world, but it works just fine.

altermetax commented on 2021-08-24 02:35 (UTC)

Done that too :)

Musikolo commented on 2021-08-24 02:11 (UTC)

It would be cool if the eclipse.ini file was only installed if none is available or no changes were made to it. This would be very helpful to keep whatever existing changes/switches we might need to add to it. Otherwise, we have to redo all those changes after each update.

altermetax commented on 2021-08-24 01:45 (UTC)

@Musikolo: done, thanks for letting me know

Musikolo commented on 2021-08-24 01:32 (UTC) (edited on 2021-08-24 01:33 (UTC) by Musikolo)

Per the documentation (readme/readme_eclipse.html), "Eclipse 4.20 requires at least a Java SE 11."

So according to that, it is my understanding that java-environment>=8 should be java-environment>=11.

Thanks.