gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Jack" <>
Subject RE: How do I turn on ant -debug from GUMP
Date Sun, 16 Mar 2003 14:39:54 GMT
Sam Ruby wrote:

	Instead of " all", try " project -debug", where you
	substitute the name of the project you are trying to build.  This will
	run interactively (no web pages produced).  You can actually specify any
	ant options on the command line, including targets and -D defines.

I get a crash when I run all in a cronjob. Annoyingly I did this,
that you suggested, and it worked. I tried it alone as a cronjob, and it
worked. So -- I have to try to debug the " all".

BTW: In case it wasn't obvious to you, I was mistaken in thinking this
turned on ant debug. I set -Ddebug=true but that didn't do the trick.

	<property name="debug" value="true"/>

So, do I just do the gen and then hack the to add -debug? Any other
way I can set it on for the individual project?

I suspect that there is very little difference between a all and a my-project -- apparently something is. Any guesses? Any guesses
from this error message?

Thanks in advance.




     [null] Created dir:
     [null] Created dir:
     [null] Created dir:
     [null] Created dir:
     [null] Created dir:
     [null] Created dir:
     [null] Created dir:
Caught exception (java.lang.NullPointerException) while expanding
lib.fileset.export.jars: null
Caught exception (java.lang.NullPointerException) while expanding
lib.fileset.export.supplied: null

View raw message