Make sure that your product or your feature(s) includes all required dependencies.Ī change in the product Dependencies tab is not reflected in the run configuration (e.g., a new plug-in is added but is not included in the run configuration)Ī product updates an existing run configuration if you start the product directly from the product definition file. Runtime configuration is frequently missing required plug-ins This option allows you to see errors from Eclipse based applications in the Console view of the Eclipse IDE. In most cases also triggered by a missing plug-in dependency.Ĭheck if your run configuration includes the -consoleLog parameter. See "Could not resolve module" message during start up error.
": No application id has been found." message during start up. Check the MANIFEST.MF file on the Overview tab in the Execution Environments section which Java version is required.
#Eclipse development how to
See the beginning of this section for a description how to solve the problem.īundles may also require a certain version of the Java virtual machine, e.g., a bundle may require Java 1.6 and will therefore not load in a Java 1.5 VM. Make sure that your product defines dependencies to all required plug-ins or features. "Could not resolve module" message during start up.Ĭheck that all required plug-ins are included in your product configuration.
The following table lists potential problems and solutions.
0 kommentar(er)
