Bug#587657: locally installed plugins aren't loaded
niels at thykier.net
Tue Mar 15 22:10:04 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
On 2011-03-15 21:10, Borden Rhodes wrote:
> Is this bug still being worked on? [...]
Personally I am hoping for a solution from upstream here; at best we
can hope to provide some fragile scripts that on a best effort basis
attempts to repair the bundles files.
It would be a much better solution if upstream anticipated this kind
of setup and these possible mismatches. Especially since we are much
less likely to be able to create a solid solution to assist in a 3.5 ->
3.6 migration (or similar).
> I don't know if I have the same
> cause but I have the same symptoms. I got a new computer, installed
> Eclipse, moved my ~/.eclipse folder over to the machine and, same as
> the initial bug report, the local plug-ins show up in "Installed
> Software" they're not accessible in Eclipse. If I wipe ~/.eclipse and
> start fresh, I can reinstall the plug-ins but this is pretty
> inconvenient since I have quite a few and configured just the way I
> want them.
> I'm using Eclipse 3.5.2-9 (Wheezy) on a 64-bit processor (which may be
> relevant since my old laptop was a 32-bit system...)
> With thanks!
I have a feeling eclipse does not support this kind of thing.
~/.eclipse/ is filled with paths and user dependent stuff. An example:
grep -r $USER ~/.eclipse/
That command will fill your screen with things that are dependent on
your username alone. If you check for "workspace" in ~/.eclipse/ it
also comes up with a couple of binary files that matches (at least in my
I would definitely not be surprised if some of this is also
architecture dependent. Actually, if you search for "x86" (at least on
an i386) you will probably see something like. So I am actually
rather confident that it is definitely architecture dependent.
On a related note, I noticed eclipse apparently dumped a lot of class
files in my ~/.eclipse, which I am trying to investigate why has happened.
You are very welcome to help us locate files that contains actual user
settings; it could very well help us inform users how (or possibly even
partly automate) to migrate preferences from 3.5 to 3.6 when we get 3.6
ready. Though these preferences are likely to be "plugin" dependent.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the pkg-java-maintainers