ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Pfeiffer (JIRA)" <>
Subject [jira] [Created] (IVYDE-327) Problem when exporting the eclipse-plugins (compiler target 1.2)
Date Fri, 02 Nov 2012 13:55:12 GMT
Carsten Pfeiffer created IVYDE-327:

             Summary: Problem when exporting the eclipse-plugins (compiler target 1.2)
                 Key: IVYDE-327
             Project: IvyDE
          Issue Type: Bug
    Affects Versions: 2.2.0.beta1
            Reporter: Carsten Pfeiffer
            Priority: Trivial

This is more a development environment issue than a bug in IvyDE. 

The JDT compiler settings in the {{org.apache.ivyde.eclipse}} plugins are explicitly configured
to compile for Java 1.2 (option "Generated .class files compatibility").

When exporting that plugin (or the feature), eclipse uses ant to compile the plugin, which
happens to use the default javac compiler instead of the eclipse Java compiler. The Sun/Oracle
compilers have a little problem with target < 1.4, leading to a {{NullPointerException}}
at runtime in

The issue in SettingsSetupEditor is it creates an anonymous subclass of {{PathEditor}}, reimplementing
its createText() method. That method is directly called in the PathEditor constructor. Inside
the createText() reimplementation, you access fields from the outer instance SettingsSetupEditor
(errorDecoration, settingsTextDeco). With target 1.2 or 1.3, the other instance is not available

	at org.apache.ivyde.eclipse.ui.SettingsSetupEditor.access$0(
	at org.apache.ivyde.eclipse.ui.SettingsSetupEditor$1.createText(
	at org.apache.ivyde.eclipse.ui.PathEditor.<init>(
	at org.apache.ivyde.eclipse.ui.SettingsSetupEditor$1.<init>(
	at org.apache.ivyde.eclipse.ui.SettingsSetupEditor.<init>(
	at org.apache.ivyde.eclipse.ui.SettingsSetupTab.createSetupEditor(
	at org.apache.ivyde.eclipse.ui.AbstractSetupTab.<init>(
	at org.apache.ivyde.eclipse.ui.SettingsSetupTab.<init>(
	at org.apache.ivyde.eclipse.cpcontainer.IvydeContainerPage$1.<init>(
	at org.apache.ivyde.eclipse.cpcontainer.IvydeContainerPage.createControl(
	at org.eclipse.jface.wizard.WizardDialog.updateForPage(
	at org.eclipse.jface.wizard.WizardDialog.access$4(
	at org.eclipse.jface.wizard.WizardDialog$

I suggest changing the target to 1.4 to avoid these problems or somehow ensure that the plugin
gets always compiled with the eclipse java compiler, even on PDE export.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message