Return-Path: X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C90ADCAA for ; Fri, 2 Nov 2012 15:21:12 +0000 (UTC) Received: (qmail 76203 invoked by uid 500); 2 Nov 2012 15:21:12 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 76176 invoked by uid 500); 2 Nov 2012 15:21:12 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 76165 invoked by uid 99); 2 Nov 2012 15:21:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 15:21:12 +0000 Date: Fri, 2 Nov 2012 15:21:12 +0000 (UTC) From: "Carsten Pfeiffer (JIRA)" To: notifications@ant.apache.org Message-ID: <807565601.60614.1351869672342.JavaMail.jiratomcat@arcas> In-Reply-To: <1300029002.60374.1351864512765.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (IVYDE-327) Problem when exporting the eclipse-plugins (compiler target 1.2) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IVYDE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489478#comment-13489478 ] Carsten Pfeiffer commented on IVYDE-327: ---------------------------------------- Sorry for the noise -- this appears to be actually an Eclipse problem. The MANIFEST.MF of org.apache.ivyde.eclipse specifies J2SE-1.4 as minimum execution environment. And this seems to be driving the PDE export options, no matter what you configure in the compiler options of the project. I'll file a bugreport at eclipse. > Problem when exporting the eclipse-plugins (compiler target 1.2) > ---------------------------------------------------------------- > > Key: IVYDE-327 > URL: https://issues.apache.org/jira/browse/IVYDE-327 > Project: IvyDE > Issue Type: Bug > Affects Versions: 2.2.0.beta1 > Reporter: Carsten Pfeiffer > Priority: Trivial > Fix For: 2.2.0.beta1 > > > 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 SettingsSetupEditor.java. > 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 though: > {code} > java.lang.NullPointerException > at org.apache.ivyde.eclipse.ui.SettingsSetupEditor.access$0(SettingsSetupEditor.java:59) > at org.apache.ivyde.eclipse.ui.SettingsSetupEditor$1.createText(SettingsSetupEditor.java:86) > at org.apache.ivyde.eclipse.ui.PathEditor.(PathEditor.java:73) > at org.apache.ivyde.eclipse.ui.SettingsSetupEditor$1.(SettingsSetupEditor.java:83) > at org.apache.ivyde.eclipse.ui.SettingsSetupEditor.(SettingsSetupEditor.java:83) > at org.apache.ivyde.eclipse.ui.SettingsSetupTab.createSetupEditor(SettingsSetupTab.java:39) > at org.apache.ivyde.eclipse.ui.AbstractSetupTab.(AbstractSetupTab.java:83) > at org.apache.ivyde.eclipse.ui.SettingsSetupTab.(SettingsSetupTab.java:35) > at org.apache.ivyde.eclipse.cpcontainer.IvydeContainerPage$1.(IvydeContainerPage.java:291) > at org.apache.ivyde.eclipse.cpcontainer.IvydeContainerPage.createControl(IvydeContainerPage.java:291) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1247) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228) > [...] > {code} > 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: http://www.atlassian.com/software/jira