Community
Participate
Working Groups
200406090800 - new workspace, File > Import > External Plugins and Fragments - Import As: Projects with source folders - import org.eclipse.swt and required plug-ins => neither og.eclipse.swt nor org.eclipse.swt.win32 contain .java files
This is normal and has always been like that. PDE does not have the info to figure out the funky setup that SWT requires (in the repo all the code is in the plugin, and it is then redistributed over the fragments at build time), therefore it automatically imports it as binary instead on importing something that it could not get to compile and let you struggle with the compile errors. Moving to pde-ui.
Correct. With the way swt is shipped, its code is spread across the plug-in and fragments and they reference each other. So it will result in circular dependencies among projects, and these are at minimum marked as warnings by the compiler. To avoid these headaches, we always import swt as binary. Will be a README in 3.0.
will use this defect to track README for org.apache.ant, org.eclipse.osgi.util and org.eclipse.osgi.services as well.
*** Bug 64068 has been marked as a duplicate of this bug. ***
Entered a readme entry for 3.0