Bug#351729: (no subject)

[Michael Koch]

severity 351729 minor
thanks


Hello Alexander,

> I believe the "bug" is resolved with this. Do you know a way to work around 
> this issue? I don't want to mount /home executable. Do I have an influence on 
> where those things are written to? Why does Eclipse write Shared Libraries 
> and so on to /home?

I don't call this "resolved", I call this "analyzed". The OSGi part of
Eclipse unpacks the native SWT libraries somewhere where it thinks it
cat load the library. It's not possible to load native libraries from
inside jars. So it writes them to a configuration site. The default
writable configuration site is in

$HOME/.eclipse/org.eclipse.platform_$(VERSION)/configuration

A solution to this solution would be to unpack the SWT jars and provide
them as a directory tree. We think about this for a longer time already.
Unfortunately it is not that easy to implement. I downgrade this to a
minor bug for now so we dont forget about it.


Cheers,
Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/