Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 442427 - [target] Target platform editor complains cannot find org.eclipse.emf although it's in luna repo
Summary: [target] Target platform editor complains cannot find org.eclipse.emf althoug...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-23 07:13 EDT by Marcel Bruch CLA
Modified: 2019-09-09 18:24 EDT (History)
3 users (show)

See Also:


Attachments
target platform (416.90 KB, image/png)
2014-08-23 07:13 EDT, Marcel Bruch CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel Bruch CLA 2014-08-23 07:13:46 EDT
Created attachment 246278 [details]
target platform

we are frequently struggling with updating the target platform because neither the editor nor problems view or error log provide enough information what's wrong with the current file (if anything at all).

The attached screenshot shows a situation where PDE complains emf could not be found. This error is displayed on all update sites (not only on the one that should actually import it). The error does not provide sufficient information that allows a releng to spot the cause of the problem.


I guess there is much more information available inside the editor, right? Please make more content available for further debugging.
Comment 1 Curtis Windatt CLA 2014-09-02 14:31:40 EDT
The software sites are resolved together (so that the same bundles are not downloaded multiple times for the different sites).  The error means the planner couldn't find a required IU (besides saying which IU has a dependency on the missing item, I'm not sure what other information you expect).  As far as I am aware, we are returning all of the error information p2 provides us.

Can you attach the target definition?  Perhaps Vikas or someone will have time to debug through P2TargetUtils.java to see if the p2 engine has any additional error information.
Comment 2 Sébastien Gandon CLA 2014-10-08 05:23:46 EDT
I have some strange behavior when using the Target Platform editor too.
One of my target file is working fine, and I copy it to some other folder in my project and then I get "unable to locate installable unit" for all my features.
This is giving me headaches cause I do not know how to fix this.

Can some tell me where is located the bundle pool ?
Comment 3 Vikas Chandra CLA 2014-10-08 07:01:43 EDT
Try increasing the sequence number by 1 in target file. Open the file in text editor

If
sequenceNumber="1"
change it to sequenceNumber="2"

Does this work?
Comment 4 Sébastien Gandon CLA 2014-10-08 08:37:22 EDT
I already did try that without luck.
by the way what is the meaning of this sequence number ?
Comment 5 Curtis Windatt CLA 2014-10-08 09:50:48 EDT
(In reply to Sébastien  Gandon from comment #2)
> I have some strange behavior when using the Target Platform editor too.
> One of my target file is working fine, and I copy it to some other folder in
> my project and then I get "unable to locate installable unit" for all my
> features.
> This is giving me headaches cause I do not know how to fix this.
> 
> Can some tell me where is located the bundle pool ?

\Workspace\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool

You should file a separate bug report for this issue.

(In reply to Sébastien  Gandon from comment #4)
> I already did try that without luck.
> by the way what is the meaning of this sequence number ?

It is to check whether the cached p2 profile is up to date with your target definition.  If the number doesn't match, we know to query the remote repository and rebuild your target.  If they match, we don't start that long running operation.
Comment 6 Eclipse Genie CLA 2019-09-09 18:24:47 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.