Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353348

Summary: Install/import from existing installation fails to produce expected choices when 3.6 is the source
Product: [Eclipse Project] Equinox Reporter: Eric Rizzo <eclipse-bugs>
Component: p2Assignee: Meng Xin Zhu <kane.zhu>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: P3 CC: didierloiseau+eclipse
Version: 3.7   
Target Milestone: Juno M2   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Attachments:
Description Flags
p2 profile none

Description Eric Rizzo CLA 2011-07-28 13:22:05 EDT
Mac OS X (10.6), Eclipse Indigo (3.7) 64-bit
When I select File > Import > Install > From Existing Installation and then select a 3.6 64-bit installation as the source to install from, the only choice offered in the list of items to install is "Eclipse SDK" even though there are lots of other features installed into that 3.6 location. If I select any of a number of other 3.5 and 3.4 installations I have, I see a more complete list of choices.
The 3.6 installation I have started out as a "Eclipse IDE for Java EE Developers" but I've installed numerous eclipse.org and third-party features into it over time. I expected to see the additional features/plugins available to install into my 3.7
This has been reported on the forums by at least 1 other person.
Comment 1 Meng Xin Zhu CLA 2011-08-02 22:15:49 EDT
Could you check the value of key 'eclipse.p2.profile' in configuration/config.ini of your 3.6 installation?  Assuming the value is 'SDKProfile', could you attach the latest .gz file from <eclipse install location>/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile/?

If the default profile name is not 'SDKProfile', use the real name to replace it in above location.
Comment 2 Didier Loiseau CLA 2011-08-07 10:16:53 EDT
I have the same issue on W7 with a previous install of Eclipse Helios JEE 32bits.

I uploaded the file you requested here:
http://www.2shared.com/file/CQTjXwnS/epppackagejeeprofile.html

(my profile name was “epp.package.jee”)
Comment 3 Eric Rizzo CLA 2011-08-08 09:04:08 EDT
Created attachment 201077 [details]
p2 profile

My config.ini value is
eclipse.p2.profile=epp.package.jee
I've attached the most recent .gz as requested above (dated Jul 12, 2011 on my machine).
Comment 4 Meng Xin Zhu CLA 2011-08-13 03:00:01 EDT
There is a workaround to modify your original Eclipse to make it work again,

1. check the value of property 'eclipse.p2.profile' from <your original eclipse loc>/configuration/config.ini. Here assuming the value is 'epp.package.jee'
2. Then go to directory <your original eclipse install location>/p2/org.eclipse.equinox.p2.engine/profileRegistry/, remove all directories except 'epp.package.jee.profile'. Technically those profile data never are used by your eclipse, they were created by release process. Anyway pls backup those directories before removing it to avoid damaging your eclipse.
3. Retry 'Install From Installation' in Eclipse 3.7
Comment 5 Meng Xin Zhu CLA 2011-08-13 04:21:54 EDT
released in HEAD
Comment 6 Didier Loiseau CLA 2011-08-13 07:32:41 EDT
Thank you for the workaround, worked perfectly!
Comment 7 Eric Rizzo CLA 2011-08-14 19:19:47 EDT
Since this was an "advertised" feature of 3.7 and the Java EE IDE package is by-far the most popular 3.6 package, I think the fix needs to be applied to the 3.7 branch and made available in the Indigo SR1 release.