I have exactly the same problem that Mario (mario-gleirscher) reported on 2022-11-17. My Java IDE is Apache Netbeans, and if, for example, I want to look at the documentation for the Pattern class, it tries, and fails, to load the file "file:///usr/lib/jvm/java-11-openjdk-amd64/docs/api/java.base/java/util/regex/Pattern.html".
I understand that this is a design feature of Snap. However, it is also causing a serious regression in multiple pieces of widely used software. It's just NOT OK to break so much stuff, and to inconvenience so many people, over a packaging change.
Please fix this. There is no security issue in providing read-only access to documentation files.
[Edit: I see that firefox has a "firefox:system-packages-doc" connection, which allows access to /usr/share/doc. That's a step in the right direction, unfortunately that's incompatible with the way that Ubuntu manages Java releases.]
[Edit: And a workaround for those using Netbeans or similar systems. The actual java documentation is, in fact, stored under /usr/share/doc, but there's a symlink from, for example, "/usr/lib/jvm/java-11-openjdk-amd64" to "../../../share/doc/openjdk-11-jre-headless", which the snap installed application cannot traverse. It's possible, however, to configure Netbeans to look for the Javadoc under either "/usr/share/doc/openjdk-11-doc/api" or "/usr/share/doc/openjdk-11-jre-headless/api", which can be accessed, at least on my system].
I have exactly the same problem that Mario (mario-gleirscher) reported on 2022-11-17. My Java IDE is Apache Netbeans, and if, for example, I want to look at the documentation for the Pattern class, it tries, and fails, to load the file "file:/ //usr/lib/ jvm/java- 11-openjdk- amd64/docs/ api/java. base/java/ util/regex/ Pattern. html".
I understand that this is a design feature of Snap. However, it is also causing a serious regression in multiple pieces of widely used software. It's just NOT OK to break so much stuff, and to inconvenience so many people, over a packaging change.
Please fix this. There is no security issue in providing read-only access to documentation files.
[Edit: I see that firefox has a "firefox: system- packages- doc" connection, which allows access to /usr/share/doc. That's a step in the right direction, unfortunately that's incompatible with the way that Ubuntu manages Java releases.]
[Edit: And a workaround for those using Netbeans or similar systems. The actual java documentation is, in fact, stored under /usr/share/doc, but there's a symlink from, for example, "/usr/lib/ jvm/java- 11-openjdk- amd64" to "../../ ../share/ doc/openjdk- 11-jre- headless" , which the snap installed application cannot traverse. It's possible, however, to configure Netbeans to look for the Javadoc under either "/usr/share/ doc/openjdk- 11-doc/ api" or "/usr/share/ doc/openjdk- 11-jre- headless/ api", which can be accessed, at least on my system].