|
|
For some reason, this problem is now back. Building with Java 7, deploying with Java 7, so there should be no problem there. I was able to reproduce it locally, then did a 'grails clean' and the problem has gone away again - for now. Why on earth might a 'grails clean' sort this one out, unless there were classes there built with Java 6 (which there weren't)? I'm worried about this one coming back on the server, so looking for any ideas. I think I may well switch back to Java 6, as I suspect it's something to do with Java 7, but what?
|