Sam Ruby wrote:
Instead of "build.sh all", try "build.sh 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 build.sh 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 "build.sh 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 build.sh to add -debug? Any other way I can set it on for the individual project?
I'm not sure what you are trying to accomplish. Adding -debug on the build of an individual project should give you the information you need? Or do you want to add -debug on the run of a project on every subsequent run (i.e., have this option be added on every regen).
I suspect that there is very little difference between a build.sh all and a build.sh my-project -- apparently something is. Any guesses? Any guesses from this error message?
The only difference should be the number of environment variables set (all sets more), and whether the output is redirected from stdout to a html file.
- Sam Ruby
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
