Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325295

Summary:	Classpath issues with swt fragments not being found
Product:	[Eclipse Project] PDE	Reporter:	DJ Houghton <dj.houghton>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public, jeffmcaffer, tjwatson
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description DJ Houghton

2010-09-14 16:54:47 EDT

Build I20100914-0100

Tom, you said to keep an eye open for resolver/classpath issues. Here is one that I am currently having.

- running latest I-Build
- have Target Platform set to be Eclipse 3.4.2 install
- have p2 R3_4_maintenance branch checked out of CVS

There are 3 projects in my workspace (p2.ui, p2.ui.sdk and org.eclipse.test) that have errors because of incomplete build path problems. They seem to be missing the SWT Display class. (which is available in the SWT fragment)

I have checked the Target Platform and the SWT fragment is available there.

But when I expand the Plug-in Dependencies (in the Package Explorer view) for those projects, the SWT fragment is not in the list... only the regular SWT bundle. (which has no code)

All 3 bundles do a RequireBundle on org.eclipse.ui so they should get SWT and its fragment for free.

Comment 1 Thomas Watson

2010-09-14 21:16:19 EDT

I assume this is Mac?  You using cocoa build for your IDE and targeting carbon 3.4.2 build?  I don't think that should be an issue.  I will investigate.

Comment 2 Thomas Watson

2010-09-14 21:30:44 EDT

Editing your target Content, selecting the Environment tab and changing the Windowing System to by carbon works around the issue.  Not sure if this is how it has always worked or not.  Moving to PDE-UI for closure or comment.

Comment 3 Jeff McAffer

2010-09-14 21:37:58 EDT

This is a pretty classic example in the mac world.  Happens to me all the time.  What threw me on this one was DJ said that the SWT fragment showed up in the target. Typically when this happens to me the fragment is not even in the target.  But then I'm usually using a Software Site whereas DJ appears to be using an Eclipse Install as the target. 

Now just wait until you try to run something and have to mess with 32 or 64 bit...

Comment 4 DJ Houghton

2010-09-15 08:39:16 EDT

Ah, good catch! Yes, that makes sense and both of you are correct. I hadn't even thought of checking to see what type of fragment I had. (been working on Win32 too long!)

Indeed I am targeting a 3.4.2 carbon install (which is why it appears in my Target Platform) but I am running a 3.6 cocoa install.

Comment 5 Curtis Windatt

2010-09-15 16:02:07 EDT

Closing as this is a (somewhat) known issue with a workaround.  Probably is a dupe somewhere but I don't see it.