Bug 460505 - Available Software Sites Caching Bug
Summary: Available Software Sites Caching Bug
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2015-02-21 05:32 EST by Patrik Suzzi CLA
Modified: 2019-07-20 11:58 EDT (History)
2 users (show)

See Also:


Attachments
First plugin / features still visible in the repo, after deleting "FIRST" content and replacing with "SECOND" (33.19 KB, image/png)
2015-02-21 05:32 EST, Patrik Suzzi CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrik Suzzi CLA 2015-02-21 05:32:55 EST
Created attachment 250992 [details]
First plugin / features still visible in the repo, after deleting "FIRST" content and replacing with "SECOND"

There are problems with "Available Software Sites" caching local repositories.

These are the steps to reproduce the bug

1. create "FIRST" plugin+feature+category, and export it onto local repository
2. install new software, add local repo to "available software sites", then install your "FIRST" plugin
3. restart eclipse verify plugin is working and uninstall the plugin
4. delete the content of the local repository, and also delete the "FIRST" project
5. create a "SECOND" plugin+feature+category, and export onto the same local repository. 
6. Now, if you try to install from that repo, you will see the "FIRST"(deleted) plugin/features, but not the "SECOND" feature/plugin you just exported. 


7. Extra test: export your second plugin onto another local path and Install new software from that repo. You will see the correct content.

Notes: 
Version: Mars (4.5)
Build id: I20150217-0800
(might be this bug belongs to Platform UI instead of PDE UI)
Comment 1 Eclipse Genie CLA 2019-07-20 11:58:05 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.