From user-return-68898-apmail-ant-user-archive=ant.apache.org@ant.apache.org Tue Sep 15 11:40:55 2009 Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 35554 invoked from network); 15 Sep 2009 11:40:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 11:40:54 -0000 Received: (qmail 2191 invoked by uid 500); 15 Sep 2009 11:40:53 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 2114 invoked by uid 500); 15 Sep 2009 11:40:53 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 94546 invoked by uid 99); 15 Sep 2009 10:30:40 -0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of marc.wirth@sap.com designates 155.56.68.171 as permitted sender) From: "Wirth, Marc" To: "user@ant.apache.org" Date: Tue, 15 Sep 2009 12:30:00 +0200 Subject: NPE in RuntimeConfigurable.maybeConfigure() via UnknownElement after upgrade to Ant 1.7 Thread-Topic: NPE in RuntimeConfigurable.maybeConfigure() via UnknownElement after upgrade to Ant 1.7 Thread-Index: Aco173qWQj+Pg719R0GtAePsdPCQsw== Message-ID: <73AFD21EA862CC46990FCB54D170E5770542824246@DEWDFECCR07.wdf.sap.corp> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanner: Virus Scanner virwal04 X-SAP: out X-Virus-Checked: Checked by ClamAV on apache.org Hello, After upgrading our environment from Ant 1.6.4 to Ant 1.7.1 we ran into Nul= lPointerExceptions with some of our custom tasks, something like: java.lang.NullPointerException=09 at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigur= able.java:390) at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigur= able.java:349) at org.apache.tools.ant.UnknownElement.handleChild(UnknownElement.java:568= ) at org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:= 346) at org.apache.tools.ant.UnknownElement.handleChild(UnknownElement.java:569= ) at org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:= 346) at org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:198) Investigating the issue we found that we created nested UnknownElement inst= ances in our implementation without explicitly setting the project except f= or the "root" element. If we explicitly set the project on each and every U= nknownElement we create then the call to configure()succeeds. I'm not sure if this should be considered a bug, but at least I couldn't fi= nd anything in the documentation that this change was intentional. From the= subversion repository this might be a side effect of change 450605 (http:/= /svn.apache.org/viewvc?view=3Drev&revision=3D450605 ) but I didn't verify t= his in detail. Googling around for the exception I only found an older thread in the JetBr= ains Developer Community ( http://www.jetbrains.net/devnet/thread/265263 ) = without a solution for the issue, though. Did anybody else experience problems with this? Should I open this as a bug= ? Best regards, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org