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 49213 - Occasional ant build failures
Summary: Occasional ant build failures
Status: CLOSED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 4.x
Hardware: Macintosh Mac OS X
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-09-17 16:47 UTC by _ tboudreau
Modified: 2006-03-24 10:06 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 _ tboudreau 2004-09-17 16:47:20 UTC
When running junit tests of a netbeans module from the IDE 
(test-single), I occasionally get this (very infrequently, maybe 
once every 50 runs):

basic-init:
files-init:
build-init:
init:
test-preinit:
test-init:
compile:
Compiling 1 source file to /space/nb_another/contrib/
navigator/build/classes
/space/nb_another/nbbuild/templates/projectized.xml:121: 
Could not create task or type of type: copy.
Ant could not find the task or a class this task relies upon.
This is common and has a number of causes; the usual 
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file: 
 - You have misspelt 'copy'.
Comment 1 Jesse Glick 2004-09-17 17:36:23 UTC
I've never seen it, nor can I guess what would cause it. If you can
reproduce it at least occasionally, try running with Verbose or Debug
mode on until it happens again.

Only happens with this kind of target? Are you running other builds in
parallel?

What OS? (The bug is marked All/All, which is assume is not really true.)
Comment 2 _ tboudreau 2004-09-18 10:13:40 UTC
I'm only sure I've seen it on test-single.

No other builds running, just repeatedly making small changes to one file and re-running 
the unit test, adding test cases and re-running the unit test, and so forth.  Running the 
test again works fine.
Comment 3 Jesse Glick 2004-09-20 15:27:44 UTC
OK, leaving open for now but I can't really do anything to investigate
it, I think. You can try running with
-J-Dorg.apache.tools.ant.module=0 to see if anything special happens
when it fails, but I can't guarantee that that logging will reveal the
problem. (Note: this logging will slow down Ant builds considerably,
so you may want to turn off sublogging of slower components - can be
identified by name of logger in [].)
Comment 4 Jesse Glick 2004-10-21 04:48:04 UTC
Haven't heard any more about it, sorry.
Comment 5 Marian Mirilovic 2005-07-12 10:12:07 UTC
closed