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 58396 - NPE in build-impl.xml when fixing code
Summary: NPE in build-impl.xml when fixing code
Status: CLOSED DUPLICATE of bug 58323
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-28 09:23 UTC by tboerkel
Modified: 2010-04-29 09:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
build-impl.xml (27.72 KB, text/plain)
2005-04-28 09:24 UTC, tboerkel 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tboerkel 2005-04-28 09:23:13 UTC 
Often, when doing "debug-fix/apply code changes", I get a NPE in build-impl.xml:

init:
deps-jar:
Compiling 1 source file to D:\4.0\Features\Packmittel\AppServer\P2Java
compile-single:
Classes to be reloaded:
 com.apag.p2plus.p2wp.ScheduleUtil
D:\4.0\Features\Packmittel\AppServer\nbproject\build-impl.xml:361: The following
error occurred while executing this line:
D:\4.0\Features\Packmittel\AppServer\nbproject\build-impl.xml:186:
java.lang.NullPointerException
BUILD FAILED (total time: 1 second)

It seems to always work OK the first time after start and mostly fail the second
time. Then I have to stop and restart the project to be able to use fix again.

Using NB 4.1 RC1 running on JDK 1.5.0_2, platform for project is 1.4.2_07.

I cannot reproduce it in a small sample.

Attaching build-impl.xml.
Comment 1 tboerkel 2005-04-28 09:24:06 UTC 
Created attachment 21905 [details]
build-impl.xml
Comment 2 Martin Entlicher 2005-04-28 18:19:17 UTC 
This is in fact a duplicate of issue #58323.

*** This issue has been marked as a duplicate of 58323 ***
Comment 3 Quality Engineering 2010-04-29 09:22:19 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.