Community
Participate
Working Groups
The default for the java emulators is still to attempt to use the embedded preverifier. At least on Eclipse 3.4, that preverifier is currently failing with a NPE. java.lang.NullPointerException at org.eclipse.core.internal.runtime.Activator.getURLConverter(Activator.java:313) at org.eclipse.core.runtime.FileLocator.resolve(FileLocator.java:186) at org.eclipse.mtj.core.internal.preverifier.EmbeddedPreverifier$PreverificationParameters.getEmptyAPI(EmbeddedPreverifier.java:158) at org.eclipse.mtj.core.internal.preverifier.EmbeddedPreverifier$PreverificationParameters.getClasspath(EmbeddedPreverifier.java:140) at org.eclipse.mtj.core.internal.preverifier.EmbeddedPreverifier.preverify(EmbeddedPreverifier.java:278) at org.eclipse.mtj.core.internal.preverifier.EmbeddedPreverifier.preverify(EmbeddedPreverifier.java:189) at org.eclipse.mtj.core.model.project.impl.MidletSuiteProject.preverify(MidletSuiteProject.java:625) at org.eclipse.mtj.core.internal.preverification.builder.ResourceDeltaBuilder.handleClassAddsAndChanges(ResourceDeltaBuilder.java:826) at org.eclipse.mtj.core.internal.preverification.builder.ResourceDeltaBuilder.handleNullDelta(ResourceDeltaBuilder.java:943) at org.eclipse.mtj.core.internal.preverification.builder.ResourceDeltaBuilder.build(ResourceDeltaBuilder.java:343) at org.eclipse.mtj.core.internal.preverification.builder.PreverificationBuilder.preverifyProject(PreverificationBuilder.java:1073) at org.eclipse.mtj.core.internal.preverification.builder.PreverificationBuilder.build(PreverificationBuilder.java:547) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360) at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516) at org.eclipse.core.internal.resources.Project.build(Project.java:94) at org.eclipse.mtj.core.model.project.impl.MidletSuiteProject.setDevice(MidletSuiteProject.java:701) at org.eclipse.mtj.ui.internal.properties.J2MEProjectPropertiesPage$1.run(J2MEProjectPropertiesPage.java:179) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Another quick look at this makes it clear that this is due to the lack of the empty API functionality. If this is not going to be made to work, then it is necessary for the user to have a different preverifier configured and that must be configured by default for the Java devices. This can't continue to be the default.
hi craig, embedded preverifier is currently not working. there are two parts missing: - port the code to use new ASM version - add the empty apis (or change the code to use the sdk stubs) we need to have an agreement about putting that to work or not, as we discussed in our past meetings. on the java sdks, we just enabled the options for the user to manually select an external preverifier. :) gep (In reply to comment #1) > Another quick look at this makes it clear that this is due to the lack of the > empty API functionality. If this is not going to be made to work, then it is > necessary for the user to have a different preverifier configured and that must > be configured by default for the Java devices. This can't continue to be the > default. >
Hi guys, Per our discussion on mail list (http://dev.eclipse.org/mhonarc/lists/dsdp-mtj-dev/msg00445.html) we decided to let the user set a default preverifier instead of using the embedded one (bug 243184). As the embedded preverifier is not being used anymore, and was replaced by the default preverifier feature, can I invalidate this bug?
Closing as the embedded preverifier is no longer going to be used.
close invalid, duplicated and wontfix bugs
