Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362653 - What causes "Could not determine SWT implementation fragment bundle"?
Summary: What causes "Could not determine SWT implementation fragment bundle"?
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 07:23 EDT by Aaron Digulla CLA
Modified: 2021-04-28 16:55 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Digulla CLA 2011-11-02 07:23:03 EDT 
Followup to the discussion on the Tycho User list:

Please change the error handling code in ProjectorResolutionStrategy.java to print more details if the search for SWT fragments fails.

For example, print the list of all IUs that start with "org.eclipse.swt" and print the filter parameters. Plus maybe a list of repositories in which you found the fragments (or didn't find them).
Comment 1 Aaron Digulla CLA 2011-11-02 07:23:55 EDT 
Wrong version :-)
Comment 2 Tobias Oberlies CLA 2011-11-07 09:55:37 EST 
I'd rather fix the root cause (bug 361901) and delete the workaround, which prints out the error, from Tycho.
Comment 3 Igor Fedorenko CLA 2011-11-07 09:59:09 EST 
(In reply to comment #2)
> I'd rather fix the root cause (bug 361901) and delete the workaround, which
> prints out the error, from Tycho.

This can only fix the problem for the new versions of SWT. We still need to support eclipse 3.4, 3.5, 3.6 and 3.7, so the workaround will have to stay for the foreseeable future.
Comment 4 Tobias Oberlies CLA 2011-11-07 10:12:03 EST 
(In reply to comment #3)
> This can only fix the problem for the new versions of SWT. We still need to
> support eclipse 3.4, 3.5, 3.6 and 3.7, so the workaround will have to stay for
> the foreseeable future.
You are totally right - we won't be able to delete the workaround. Still you probably get the point why I don't feel like working on the error message...

@Aaron: I'd review your patch though.