Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317885 - [shared] Trac connector not installing correctly in shared install
Summary: [shared] Trac connector not installing correctly in shared install
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Pascal Rapicault CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 377346 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-06-24 17:52 EDT by David Johansen CLA
Modified: 2013-02-04 21:15 EST (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Johansen CLA 2010-06-24 17:52:32 EDT
I just installed Eclipse 3.6 for the first time and tried adding a Trac repository. I installed the Trac connector, but it doesn't show up as an option when adding a new  Task List repository.

-- Configuration Details --
Product: Eclipse 1.3.0.20100617-0520 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.mylyn_feature 3.4.0.v20100608-0100-e3x
Comment 1 Steffen Pingel CLA 2010-06-24 18:40:37 EDT
Can you check if the eclipse installation is writeable to the user running Eclipse? 

I was able to reproduce this by installing the Trac connector into a shared installation. The install appeared to be successful and the Trac connector is shown in under About > Installation Details but it is not loaded (the feature was installed into ~/.eclipse/org.eclipse.platform_3.5.0_172093924/features/).
Comment 2 David Johansen CLA 2010-06-24 18:57:57 EDT
The eclipse installation (at /usr/local/eclipse-3.6/) is not writable to the user running Eclipse.

Does it have to be writable? If so, shouldn't the user be told that after the failed installation?
Comment 3 Steffen Pingel CLA 2010-06-24 19:43:48 EDT
I would expect this to work without making the directory writeable to the user. I am moving this to p2 since the problem appears to be reproducible with any feature that is installed into a shared Java EPP package.
Comment 4 Markus Knauer CLA 2010-06-25 02:08:41 EDT
I can reproduce this behaviour with other packages, in that case I tried it with the RCP/RAP package. 

Then I downloaded a plain SDK and started it read-only. In that case the SDK doesn't allow installation at all. Why does the SDK behave in a different way here? I couldn't see any substantial or suspicious differences in the .ini files.
Comment 5 Markus Knauer CLA 2010-06-25 02:43:52 EDT
Okay, I found the difference... it can be reproduced with both, the Classic/SDK *and* with the EPP packages.

There are multiple ways of installing software into your running Eclipse and they seem to be inconsistent. If you want to reproduce it with the Classic/SDK, start with a writeable install of the SDK, install Mylyn or the MPC, shut down Eclipse, make it read-only and start again.

1 - The p2 UI: Help > Install New Software...
2 - The Marketplace Client MPC
3 - Mylyn: > Add Task Repository > Install More Connectors...
4 - Modeling EPP Packages: Install additional Modeling components
5 - Maybe more that I don't know of... :)

If someone starts a read-only Eclipse, the result is as follows

1 - Doesn't show any p2 repositories, therefore it is not possible to install anything out of the box
2 - I didn't check, but I assume it is possible to install things that will never appear after a restart
3 - That is probably the scenario that is described here: Installation possible but the change is being ignored after a restart.
4 - The same as 2, 3

To make it even worse, there is not a single exception from p2 written to the log.
Comment 6 David Johansen CLA 2010-06-25 11:40:09 EDT
Before submitting the bug, I tried installing it from the Marketplace. When I first went in there, it showed up as installed, so I close Eclipse, removed all of the eclipse data from my home directory and workspace and then went back into the marketplace and installed it. It still had the same issue as installing it from "Install More Connectors..."
Comment 7 Steffen Pingel CLA 2011-04-05 16:27:15 EDT
Is this a duplicate of bug 287246?
Comment 8 Steffen Pingel CLA 2012-04-22 07:51:51 EDT
*** Bug 377346 has been marked as a duplicate of this bug. ***
Comment 9 Pascal Rapicault CLA 2013-02-04 21:15:39 EST
I think this has been fixed in the past, and if not the ongoing work on p2 to fix shared install definitely will.