-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2011-03-15 21:10, Borden Rhodes wrote: > Is this bug still being worked on? [...]
Hi 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 case). 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[1]. 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. ~Niels [1] org.eclipse.core.filesystem.linux.x86,1.3.0.R35x_v20091203-1235,plugins/org.eclipse.core.filesystem.linux.x86_1.3.0.R35x_v20091203-1235.jar,4,false [...] Binary file ../../.eclipse/org.eclipse.platform_3.5.0_155965261/configuration/org.eclipse.osgi/.bundledata.14 matches Binary file ../../.eclipse/org.eclipse.platform_3.5.0_155965261/configuration/org.eclipse.osgi/.state.14 matches Binary file ../../.eclipse/org.eclipse.platform_3.5.0_155965261/configuration/org.eclipse.osgi/.lazy.14 matches -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJNf+O8AAoJEAVLu599gGRC1/kP/A2KpiXfGW6me/6pw+sbHB1G aHywzsVoD4Z43sZDMhDNn0rGopDixNd6H/bhLX7IYKFyG1tK8vaY9zBOAG5ecq16 zlY4WZj4yT6EEcCht04Tjbe0LAR8D2GiVfBR9jgLa3NpnoCG761jpQms0YYUtdCN 6xlzUZNHGWon+QJqZCmV4RhM8cFoVhP8fJa4+SNw+UKyXYvVn+08bPEx8QigSOHu 3Xa6qk4JmHacSHFw8Bqbhor00iIhr3NsWzOetO5b7A7zPCw1GxnXDMTwuHrJ1ywI tHRh7e4kaKuc3bTieNa5dhzhFHtLAeK7tdMkmnjOuo5RQlaV0YFYd0MxqBm6sBqz zmvaNKfW4GODPfHcRBxTHzg+iyaMWSPxA58Au5KRSE/W6Lib+0VHbI2daFUEahLu FL+Q66TR+OU3rWZ6KPQSTL1lZLRMKwI3CzxwEKRSm+SCLMu07klmlF7zK6rmD6wj O/oMwE6JKc02UHNghMC8k7d13v9CuAKMtVwfpgLBlQsC0qjAdZg9SEslM3gred7P 41Rb+galPz6arb0OvE2Aaja2xKRBQpCX4cZIUNe4T2jWKKuI7H9iSPGw/4fTfh5h 1BD+HrkE/NrVuQmbN4ZW6gyjP9WF6BQwxWLar7gYGpI/FNkgHPYkuLEBeKHIvhV6 JYLulcw24BsQVyhLLLZl =X2Uq -----END PGP SIGNATURE----- __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.