Summary: | Linking to an extension install/ unlinking | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Vlad Klicnik <klicnik> |
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dejan Glozic <dejan> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P1 | CC: | celek |
Version: | 2.0 | ||
Target Milestone: | 2.0 M6 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Vlad Klicnik
2002-05-16 20:49:31 EDT
I added the first half of the function, but Core does not allow me to create the site. Scenario: 1) Create a directory d:\rational\extensions 2) Create a file d:\rational\extensions\.eclipseextension 3) Create a directory d:\rational\extensions\eclipse 4) Drill down from 'My Computer'. It will show 'extensions' as a local site and you can use pop-up menu to link to it. However, Core reports that 'eclipse' is part of anoter site and cannot be added. We need a flag to distinguish between creating a new site to install features into and linking to an existing extension site. Synch with core.boot. Contains ISiteEntry.isExternallyLinked() as api. For the "private" linking support (ie. via our UI), the method that checks whether a site can be unlinked should check the following: * the site is an extension install site (ie. contains .eclipseextension just above the local site directory (ie. above the eclipse/ directory)) * the site is not natively linked (ie. we must not allow unlinking of natively installed links) Only "privately" linked sites (ie. via our UI) can be allowed to be unlinked. Released core code. Need to verify Tries with 0517 + HEAD (0518 at 6pm). Does not work. Im an unable to add Red Dot as an extension install. What I have in the file system is Red Dot Install/ eclipse/ .eclipseextension features/ ... unzipped reddot feature plugins/ ... unzipped reddot plugin This should work for F1 (please note the file layout as per spec .... I messed this up in my original explanation of the function) Of course it does not work - the defect is still open. When I implement the code, it will work :-). Implemented as follows: 1) When drilling down My Computer object, a directory that contains .eclipseextension file is shown with a local site icon and no futhter drilling is possible. A special page for this object explains what a product extension is and what can be done with it (i.e. use pop-up menu to link it to your product). 2) Linking is performed using the new API (createLinked...). A message that restart is needed is shown. The new site immediately appears in the current configuration in 'Install Configurations' view. 3) If a site in current configuration returns true for isProductExtension and false to isNativelyLinked(), a pop-up menu action 'Unlink' appears when it is selected. When performed, it goes away and a message to restart is show. The change is now in HEAD. |