Hjem   |   Kontakt   |   Sitemap
Hvem er vi Hvad kan vi Vores kunder Ledige stillinger Kontakt os Blog

How to debug grails run-app loop

Published Wednesday, November 11th, 2009 by mil

I recently had a problem where grails run-app would start
the server, then immediately recompile 1 class, then restart… and
repeat.

Google told me that the problem probably was an empty Java file in my
project and to look in the
~/.grails/1.2-M4/projects/myproject/classes directory to
see which file kept changing timestamp.

However, no files did that. The solution was to modify
$GRAILS_HOME/scripts/_GrailsCompile.groovy and add
listFiles:true to the compile target:

ant.groovyc(destdir:classesDirPath,
classpathref:classpathId,
encoding:"UTF-8",
listFiles:true,
compilerPaths.curry(classpathId, false))

And it turned out Google was right, I had a Java file with only the
package specification in it.

Leave a Reply

Using TDC’s Columbine with modern browsers

Thursday, April 14th, 2011
On columbine.tdc.dk there is a gui with tools for resellers of TDC eBSA products. These ...

Groovy CPE

Thursday, February 3rd, 2011
I've been working quite a lot on a TR069 AutoConfigurationServer. As part of the prototyping ...
 
© 2011 Code3 ApS  |  Kigkurren 8G, 3.TH  |  2300 København S  |  +45 7020 3383  |  kontakt@code3.dk