ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15325] New: - NullPointerException with Jar task
Date Thu, 12 Dec 2002 18:26:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15325>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15325

NullPointerException with Jar task

           Summary: NullPointerException with Jar task
           Product: Ant
           Version: 1.5.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: bill.stamp@eds.com


Within a build script, I execute the "jar" task multiple times to create 
several large jar files.  After so many jar tasks (approx 6 times), the script 
takes a NullPointerException.

java.lang.NullPointerException
	at org.apache.tools.zip.ZipOutputStream.finish(ZipOutputStream.java
(Compiled Code))
	at java.util.zip.DeflaterOutputStream.close
(DeflaterOutputStream.java:139)
	at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java:402)
	at org.apache.tools.ant.Task.perform(Task.java:319)
	at org.apache.tools.ant.Target.execute(Target.java:309)
	at org.apache.tools.ant.Target.performTasks(Target.java:336)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
	at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
	at org.apache.tools.ant.Task.perform(Task.java:319)
	at org.apache.tools.ant.Target.execute(Target.java:309)
	at org.apache.tools.ant.Target.performTasks(Target.java:336)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
	at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
	at org.apache.tools.ant.Task.perform(Task.java:319)
	at org.apache.tools.ant.Target.execute(Target.java:309)
	at org.apache.tools.ant.Target.performTasks(Target.java:336)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
	at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
	at org.apache.tools.ant.Task.perform(Task.java:319)
	at org.apache.tools.ant.Target.execute(Target.java:309)
	at org.apache.tools.ant.Target.performTasks(Target.java:336)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
	at org.apache.tools.ant.Main.runBuild(Main.java:610)
	at org.apache.tools.ant.Main.start(Main.java:196)
	at org.apache.tools.ant.Main.main(Main.java:235)

Usually a jar file is created, but when attempting to open it, it fails (like 
it built the jar but didn't complete the indexing of the jar).

If I re-start my build script at the point of failure (after deleting the bad 
jar file).  It successfully creates the jar file and other subsequent jar files.

I have attempted to increase the heap size of the jvm running ant (to 256MB) to 
see if that somehow helps the situation, but with no success.  As an interim 
solution, I execute the "exec" task to perform the "jar".  That enabled me to 
get farther in my build script but now the same problem occurs when 
executing "war" tasks within my build script.  

I will attempt to do a comparable "exec" task in place of the "war" tasks, but 
it is making the script significantly more complex.

Thank you.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message