This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 29655 - Build fails with NPE in NB 3.4.1 RC1
Summary: Build fails with NPE in NB 3.4.1 RC1
Status: VERIFIED INVALID
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: issues@projects
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-19 18:38 UTC by oneway
Modified: 2005-07-15 07:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description oneway 2002-12-19 18:38:58 UTC
Build fails with NPE in NB 3.4.1 RC1 (see related messages 
below).
The same build completes successfully in NB 3.4
P1 (for me) since this is pretty serious regression and 
some apps can no longer be built from NB 3.4.1

------------------------------------------
...
Unable to load dependency analyzer: 
org.apache.tools.ant.util.depend.bcel.AncestorAnalyzer
building ejb.jar with 9 files
...
...
java.lang.NullPointerException
        at sun.tools.javac.Main.compile(Compiled Code)
        at sun.tools.javac.Main.main(Main.java:465)
Exec failed .. exiting
build.xml [235] Exception while calling weblogic.ejbc20. 
Details: Ejbc reported an error
BUILD FAILED
Comment 1 Jesse Glick 2002-12-19 18:55:07 UTC
You're going to have to provide steps to reproduce the exception from
scratch - probably you are the only person to get it, and we cannot
just guess why a NPE would be thrown from a method in the Javac
implementation. For starters, run with verbosity set to Verbose or
Debug and include the full output log; also your system/ide.log. That
might provide some kind of clue. But most likely it will be necessary
to have a complete test case.

Were you using Ant 1.5.1 in NB 3.4? 3.4.1 includes Ant 1.5.1 by
default (for 3.4 you can get it from the Update Center). Maybe you are
seeing a problem in Ant 1.5.1 (or in your build script as triggered by
Ant 1.5.1). Please check using command-line Ant that your script works
correctly under either 1.4.1 or 1.5.1.
Comment 2 oneway 2002-12-19 21:29:52 UTC
You're right, this is an issue with Ant 1.5.1. Changing 
status to INVALID.
Comment 3 Marian Mirilovic 2005-07-15 07:43:36 UTC
closed