Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355937 - [p2] "Install into host repository" often doesn't work
Summary: [p2] "Install into host repository" often doesn't work
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-26 07:49 EDT by Nicolas Bros CLA
Modified: 2019-10-07 03:56 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Bros CLA 2011-08-26 07:49:47 EDT
Most of the time, when I try to export a plug-in into my running environment or another install, I get an error.

The error message is (for example):
Could not find the exported unit with id: org.eclipse.emf.facet.dev.core version: 0.1.1.201108261345

This does not say why it is failing though. So I don't know whether this is an internal error in PDE, or if some unmentioned precondition for installation was not met.


Eclipse SDK
Version: 3.7.0
Build id: I20110613-1736
Comment 1 Curtis Windatt CLA 2011-08-26 10:35:53 EDT
The error is coming from p2 when we try to create the repository. I do not know if it indicates that PDE has done something wrong in the setup or if p2 is missing some piece that the content you are trying to install requires.
Comment 2 Nicolas Bros CLA 2011-10-27 11:05:26 EDT
I get this error all the time.
How can I get more information (log?) when that happens?
Comment 3 Sebastian Zarnekow CLA 2012-07-10 03:23:52 EDT
I have the very same problem. Any hints on how to tackle the issue?
Comment 4 Curtis Windatt CLA 2012-07-10 11:06:59 EDT
This issue needs the involvement of someone more familiar with p2.
Comment 5 Eclipse Genie CLA 2019-10-07 03:56:56 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.