Community
Participate
Working Groups
Steps to reproduce this bug : 1. create a new empty workspace 2. go to the target platform configuration and add a new empty target definition 3. in this target definition, add a new update site and import a feature X from it (OK => the feature X is resolved) 4. in this target definition, add another update site an import another feature Y from it (KO => message "Unable to locate installable unit X" - for each update site defined in the target definition) My Windows computer is behind an NTLMV2 proxy, so I added the following option in "eclipse.ini" to let Eclipse access p2 update sites successfully (after -vmargs ) : -Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclient4
What release is this in 4.4.0? Please provide more detailed explanation of what IU is missing, and how they relate to the selected content. Since you are getting the 'unable to locate' message on both of the update sites, I suspect this is working as desgined. If you only have feature Y selected, does it work or is IU x still missing? All of the update sites are queried for all of the selected IUs together in one operation. So having multiple sites should not cause things to be missing. However, if you have 'include required software' checked, all dependencies for all selected IUs must be available in at least one update site.
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.
