Closed klinger closed 9 years ago
I cant really reproduce it - have this weird behaviour for weeks and with different ceylon versions and operating systems. (win7, win8, linuxmint), i even tried different java versions. Closing Eclipse often doesnt help. Creating new projects didnt get me nearer to the problem.
I am still not convinced its really a ceylon problem. At some point my projects get this NPE message and I have to compile them out of the IDE to create the modules - then I am able to run the modules in the IDE.
I
@klinger we need a stack trace. Can you find one in the Eclipse logs?
I am not sure whether this shows in the log. I close the project, close eclipse, open eclipse again, open the project, press clean project - there is no error in the error log.
I get some errors though at other times: eclipse.buildId=4.4.2.M20150204-1700 java.version=1.7.0_79 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
org.eclipse.ui.views.properties.tabbed Error Mon May 25 15:32:48 CEST 2015 Contributor com.redhat.ceylon.eclipse.ui.view.CeylonExplorer cannot be created.
org.eclipse.core.runtime.CoreException: Plug-in "com.redhat.ceylon.eclipse.ui" was unable to instantiate class "org.eclipse.ui.internal.navigator.resources.workbench.TabbedPropertySheetTitleProvider".
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyRegistry.
and
eclipse.buildId=4.4.2.M20150204-1700 java.version=1.7.0_79 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
org.eclipse.equinox.registry Error Mon May 25 15:32:48 CEST 2015 Plug-in "com.redhat.ceylon.eclipse.ui" was unable to instantiate class "org.eclipse.ui.internal.navigator.resources.workbench.TabbedPropertySheetTitleProvider".
java.lang.NullPointerException
at org.eclipse.ui.internal.navigator.resources.workbench.TabbedPropertySheetTitleProvider.
Does it remember errors? I have one from yesterday:
eclipse.buildId=4.4.2.M20150204-1700 java.version=1.7.0_79 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
org.eclipse.core.jobs Error Mon May 25 00:31:41 CEST 2015 An internal error occurred during: "Typechecking the working copy of test/run.ceylon".
java.lang.NullPointerException
at com.redhat.ceylon.eclipse.core.builder.CeylonProjectConfig.initMergedConfig(CeylonProjectConfig.java:85)
at com.redhat.ceylon.eclipse.core.builder.CeylonProjectConfig.
Could be from here:
private void initMergedConfig() {
mergedConfig = CeylonConfig.createFromLocalDir(project.getLocation().toFile());
mergedRepositories = Repositories.withConfig(mergedConfig);
}
wdyt, @davidfestal ?
I don't see how the CeylonProjectConfig
error is related to the main issue.
It seems that this error can appear when the project is removed from the workspace in the meantime, though a project file is still in an editor and is parsed.
I can try to fix, this, but this will probably not fix the issue itself.
@klinger : we don't have any stackTrace that seems to be relevant to the main issue problem. Does it still happen ? and did you finally find a way to reproduce it systematically ?
Closing since there was not answer. @klinger : please reopen it if you encounter the problem again.
I get an error message in eclipse: "The Ceylon Java backend compilation failed with a throwable: java.lang.NullPointerException" as Ceylon Backend Error in line 0.
My Setup: build IDE from sources yesterday, but got this before with 1.1 on linux and windows machine too. It think MY problem here is part of using mixed modules. If I import a 1.1.1 module:
native("jvm") import ceylon.net "1.1.1";
i cannot use any 1.1.0 modules anymore. Is this intended? I always thought the modular system would allow such mixture. Is there a way to get a better error message?