On 17 Jul 2008, at 20:17, Graeme Rocher wrote:
> I would say the problem is caused by this code in Package.groovy
>
> // Get the application context path by looking for a property
> named 'app.context' in the following order of precedence:
> // System properties
> // application.properties
> // config
> // default to grailsAppName if not specified
>
> serverContextPath = System.getProperty("app.context")
> serverContextPath = serverContextPath ?:
> Ant.antProject.properties.'app.context'
> serverContextPath = serverContextPath ?: config.grails.app.context
> serverContextPath = serverContextPath ?: grailsAppName
>
>
UGH. Ugh indeed.
"config.grails.app.context" is not the problem. If you set that, it
still fails. It does -not- fail if you set -Dapp.context=xxx
So the problem is the Ant properties line, it seems. Which... isn't so
easy to workaround is it.
Why is this broken for some projects and not others? I have one 1.0.3
project (also upgraded from 1.0.2) that requires no workarounds?
Marc
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
