Classic confinement request for eclipse

Eclipse is a popular IDE, and relies on many external tools (such as the JRE/JDK). The repo is and the store page is .

This feels like a similar use case to our other graphical IDEs such as Pycharm, IntelliJ, VS Code and Atom which are all also classic.

I agree that this warrants classic. Like the other IDEs mentioned, users of Eclipse have an expectation that it can access files anywhere on the filesystem. It needs to be able to call binaries that cannot all be known prior to installation.

I’m +1.

As per Process for reviewing classic confinement snaps, step 1, this should be in the #store category


Granting use of classic. This is now live.

The next upload will pass automated review. r1 was rejected, so either upload a new revision or request a manual review of r1 in the store.

1 Like

Thank’s very much!

@popey @jdstrand should snaps like eclipse include a JRE? Or how can we simplify the process for users to install such dependencies?

See also

all snaps need to be self-contained and should ship all their dependencies or use the correct extensions/content-snaps … this is by design, the type of confinement does not make a difference here …