Bug 470 - Eclipse plug-in installation issues:
Summary: Eclipse plug-in installation issues:
Status: VERIFIED FIXED
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 0.9 M4
Assignee: Lianhao Lu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-10-14 15:45 UTC by Jessica
Modified: 2010-12-21 05:59 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica 2010-10-14 15:45:30 UTC
1. It seems allow more than one instance of our SDK plugin installed in the Eclipse IDE, should detect whether there's already one installed then either bail out or provide choice to install over if it's a newer version

2. In Help-> About Eclipse SDK-> Installation Details, click on Features tab, for our plugin, there's no Provider and Feature Name entries.  Also, under Plug-ins tab, our provider is Intel.  Please change all Provider fields to yoctoproject.org, and our plugin name to Yocto Plugin
Comment 1 Lianhao Lu 2010-10-14 18:35:54 UTC
(In reply to comment #0)
> 1. It seems allow more than one instance of our SDK plugin installed in the
> Eclipse IDE, should detect whether there's already one installed then either
> bail out or provide choice to install over if it's a newer version
> 

Jessica, what do you mean by saying "allow more than one instance of our SDK plugin installed in the Eclipse IDE"? I think the update manager will detect if you try to install the same version of plugin.
Comment 2 Jessica 2010-10-14 20:29:28 UTC
Somehow the update manager didn't detect in my Eclipse IDE, so I ended up with two Yocto SDK installed.  If you can't reproduce this situation, please fix the 2nd issue reported in this bug
Comment 3 Lianhao Lu 2010-10-14 20:47:10 UTC
Can not reproduce the 1st issue with eclisep 3.6, on x86_64 or x86 host, ubuntu 10.04.

The 2nd issue is fixed in commit b52ddb0.
Comment 4 Lianhao Lu 2010-10-14 20:48:31 UTC
(In reply to comment #3)
> Can not reproduce the 1st issue with eclisep 3.6, on x86_64 or x86 host, ubuntu
> 10.04.
> 
> The 2nd issue is fixed in commit b52ddb0.

Typo. The fixing commit should be 7146fa3.
Comment 5 Jessica 2010-10-14 21:04:30 UTC
Lianhao, can you build a zip file from the latest plugin code and send it over to me for me to verify? thx.
Comment 6 Lianhao Lu 2010-10-15 00:26:24 UTC
I did the following test:

1. ran the headless build to generate a new archive zip, version is 1.0.0.201010151237
2. installed the plugin through IDE
3. ran the same headless build again to generate a new archive zip, version 1.0.0.201010151451
4. installed the new plugin. The IDE will upgrade the plugin due to the newer version number. 

It looks like the 1st issue (multiple instances of plugin got installed) can not be reproduced. 

Jessica, what are the version numbers of your 2 installed plugins?
Comment 7 Jessica 2010-10-16 20:53:00 UTC
Ignore my case since my older version of plugin is generated by my update project so is not following the same release naming convetion as the headless build.  But one more test case please verify, that is now with a newer version of plug in installed, if you tried to install the older version of the plugin, the upgrade manager should be able to detect it, please confirm.  If that case is handled correctly, please mark the bug fixed.  Thx
Comment 8 Lianhao Lu 2010-10-17 19:17:08 UTC
Tested installing an older version of our plugin when a newer version is already installed, this could be detected by the update manager and proper information was displayed telling the user of the situation.
Comment 9 Jessica 2010-10-21 00:54:48 UTC
Verified with the latest eclipse plugin build