Bugzilla – Full Text Bug Listing
| Summary: | File>Import...>Import External Plug-ins and Fragments doesn't setup .classpath | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Simon Tardell <simon> |
| Component: | UI | Assignee: | Wassim Melhem <wassim.melhem> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
The first checkbox on the Workbench preference page does indeed turn off all builds (including background building). I'm unable to reproduce this. Could you please specify what plug-ins you were importing and what JRE you were using... I am using Sun's JDK 1.4.2_02 on RH Linux 9.0.93 (plus a bit of Rawhide...).
I am trying to import everything that is required by some third party plugin
which is this list:
org.apache.lucene
org.apache.xerces
org.eclipse.ant.core
org.eclipse.compare
org.eclipse.core.boot
org.eclipse.core.filebuffers
org.eclipse.core.resources
org.eclipse.core.runtime
org.eclipse.debug.core
org.eclipse.debug.ui
org.eclipse.help
org.eclipse.help.appserver
org.eclipse.jdt.core
org.eclipse.jdt.debug
org.eclipse.jdt.launching
org.eclipse.jdt.ui
org.eclipse.jface
org.eclipse.jface.text
org.eclipse.search
org.eclipse.swt
org.eclipse.swt.gtk
org.eclipse.team.core
org.eclipse.text
org.eclipse.ui
org.eclipse.ui.console
org.eclipse.ui.editors
org.eclipse.ui.views
org.eclipse.ui.workbench
org.eclipse.ui.workbench.texteditor
org.eclipse.update.core
(requires in the plugin.xml of the plugin:
<requires>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.jdt.ui"/>
<import plugin="org.eclipse.jdt.core"/>
</requires>
)
Just to make sure: Is this happening consistently? Yep. Tried it three or four times already. Which option in the 'Plug-ins and Fragments to import' section of the first page of the import wizard did you use? 1. Choose from all... OR 2. Import plug-ins required by existing workspace plug-ins? As a workaround in the meantime, you can explicitly update the classpath of the projects you importing by right-clicking on the plugin.xml file and selecting 'Update Classpath..' from the context menu. I've tried both methods with the same result. Workaround works (thanks). |
I recently did a fresh install of 3.0M4 on a new machine (RHL 9.0.93), and tried to do some plugin development. I imported the plugin I wanted to work on, and then did a "File>Import...>Import External Plug-ins and Fragments" to pull in all dependencies. I tried both binary, binary with linked contents and source. In all cases the projects come up with basically empty .classpath: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="output" path="bin"/> </classpath> When I compare with earlier what was previously generated by older releases (2.1-3.0M3) there is a whole lot missing: references to the source folder or jars, dependencies on other plugins and the runtime libraries. This appears to be similar to Bug 42118 except that it appears in 3.0M4, and as far as I understand, background builds are off (is that the first check box on the Workbench preference page?).