[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] more feature patch installation woes
- From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
- Date: Tue, 11 Jan 2011 10:17:29 -0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:date:x-google-sender-auth:message-id :subject:from:to:content-type; b=uzxQMdi6xQ0kMeaaMhzTLf5Thw1rFiNcXDvDlY5RKJyKtSPL+PkwaGyNm93i/0iXHa ST7RhMzzlgw1s0l9jTJBYHSDqoXweGpNT0S33URQiz91N+Qx07DcwqVaeKqKAgvU40Td OJ25exlBRTzaMendhRiDh7lrqTvYgMSG14rlU=
A short while ago, I mentioned some problems that some of my users are
having when trying to install Groovy-Eclipse into a read-only
directory (Groovy-Eclipse ships with a feature match for jdt.core).
There is another problem, that is happening that is perhaps even more
perplexing. After some windows users install Groovy-Eclipse, the
entry for org.eclipse.jdt.core is removed from the bundles.info file
(it should have been replaced with the new entry for the patched
jdt.core bundle). Unfortunately, I can't reproduce it myself, but I
am wondering if anyone has any idea what is happening here.
I just raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=334012.
Here is the original issue about read-only installations:
I am a bit perplexed as to what is happening here. Any ideas?