1.2-M4 and java.util.logging

[Robert Fletcher]

Has something changed with the way java.util.logging is handled by
Grails in 1.2-M4? When I run tests using the selenium-rc plugin with
1.2-M3 and below I get nice neat output, with 1.2-M4 and the current
snapshot I get a huge amount of noise from the selenium client driver
which uses JUL.

Cheers,
Rob

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Robert Fletcher]

Aha, just stumbled on the grails.logging.jul.usebridge = true config
setting and everything's back to normal again.

When upgrading it seems to actually be a good practice to run 'grails
init' and manually merge in changes to things like DataSource,
Bootstrap, Config, etc. to pick up new things like this.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Graeme Rocher-3]

I did this because of http://jira.codehaus.org/browse/GRAILSPLUGINS-1546

Don't know if it has actually fixed that problem yet

Cheers

On Sun, Nov 8, 2009 at 10:53 AM, Robert Fletcher
<robert.w.fletcher@...> wrote:

> Aha, just stumbled on the grails.logging.jul.usebridge = true config
> setting and everything's back to normal again.
>
> When upgrading it seems to actually be a good practice to run 'grails
> init' and manually merge in changes to things like DataSource,
> Bootstrap, Config, etc. to pick up new things like this.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

--
Graeme Rocher
Head of Grails Development
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Marc Palmer Local]

On 8 Nov 2009, at 14:27, Graeme Rocher wrote:

> I did this because of http://jira.codehaus.org/browse/GRAILSPLUGINS-1546
>
> Don't know if it has actually fixed that problem yet

Maybe we can improve things here.

What if there was a standard script: "grails diff-config" that would  
run a configslurper to load the app's Config.groovy and the Grails  
default Config.groovy, and output the differences of the evaluated  
data (reverse coded back into script code, not just a dump of hashmaps).

Then the grails upgrade script could make use of this at the end of  
its processing, to give people a chance to merge stuff in (and remind  
them).

A DSL might be better though, but more work. Declarative definition of  
templates with help info":

configItem 'grails.logging.jul.usebridge = true', "Enable JUL -> Log4j  
bridging"
configItem 'grails.gorm.save.failOnError = true', "Enable failfast  
exceptions when obj.save() fails"

Obviously the more complex configs would require a little more  
thought, but the above approach would allow upgrade to optionally auto-
merge stuff (after evaluating if there is any assignment to the listed  
config items).

Marc
~ ~ ~
Marc Palmer
Blog         > http://www.anyware.co.uk
Twitter      > http://twitter.com/wangjammer5
Grails Rocks > http://www.grailsrocks.com







---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email