reloading of static files in Grails 1.4.0.M1

[rlovtangen]

I'm running 'grails run-app' with Grails 1.4.0.M1, and can't get changes to main.css to reload. I have to shutdown and run 'grails run-app' again for the changes to appear.
Am I doing something wrong?
I don't think it's browser cache related, tried to open the application in some other browsers that had newer run this particular application before, and main.css looked exactly like it did on last 'grails run-app'.

Ronny

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

    http://xircles.codehaus.org/manage_email

[burtbeckwith]

What OS?

Burt

> I'm running 'grails run-app' with Grails 1.4.0.M1, and can't get changes to main.css to reload. I have to shutdown and run 'grails run-app' again for the changes to appear.
> Am I doing something wrong?
> I don't think it's browser cache related, tried to open the application in some other browsers that had newer run this particular application before, and main.css looked exactly like it did on last 'grails run-app'.
>
> Ronny

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

    http://xircles.codehaus.org/manage_email

[rlovtangen]

Mac OS X, snow leopard

Den 22. juni 2011 kl. 14:00 skrev Burt Beckwith <[hidden email]>:

> What OS?
>
> Burt
>
>> I'm running 'grails run-app' with Grails 1.4.0.M1, and can't get changes to main.css to reload. I have to shutdown and run 'grails run-app' again for the changes to appear.
>> Am I doing something wrong?
>> I don't think it's browser cache related, tried to open the application in some other browsers that had newer run this particular application before, and main.css looked exactly like it did on last 'grails run-app'.
>>
>> Ronny
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

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

    http://xircles.codehaus.org/manage_email

[Fran García]

Same here with MAC OS X Snow Leopard and Ubuntu 11. I cannot view the changes made on the main.css because the main layout is linked to static/css/main.css which has an old version of this file.

[virtualeyes]

grails.resources.processing.enabled = false

in config > envir > devel

see this thread for ref:
http://grails.1312388.n4.nabble.com/Re-Grails-2-0-CSS-Changes-not-Picked-Up-td3680479.html

[rlovtangen]

Thanks.

This needs to be default for run-app in development mode IMHO. It's a PITA to work with frontend without js/css reloading, and new users of Grails shouldn't need to experience this pain.

Ronny

On Jul 21, 2011, at 2:40 PM, virtualeyes wrote:

> grails.resources.processing.enabled = false
>
> in config > envir > devel
>
> see this thread for ref:
> http://grails.1312388.n4.nabble.com/Re-Grails-2-0-CSS-Changes-not-Picked-Up-td3680479.html
>
> --
> View this message in context: http://grails.1312388.n4.nabble.com/reloading-of-static-files-in-Grails-1-4-0-M1-tp3616262p3683575.html
> Sent from the Grails - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

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

    http://xircles.codehaus.org/manage_email

[felipecao]

agree with Ronny. there's also the question of existing users migrating from 1.3.7 to 1.4/2.0, that are used to have automatic reload and assume it's working the same way and hang hours until they find out the context is not getting reloaded for some reason (myself :) )

On Thu, Jul 21, 2011 at 10:05 AM, Ronny Løvtangen <[hidden email]> wrote:

Thanks.

This needs to be default for run-app in development mode IMHO. It's a PITA to work with frontend without js/css reloading, and new users of Grails shouldn't need to experience this pain.

Ronny

On Jul 21, 2011, at 2:40 PM, virtualeyes wrote:

> grails.resources.processing.enabled = false
>
> in config > envir > devel
>
> see this thread for ref:
> http://grails.1312388.n4.nabble.com/Re-Grails-2-0-CSS-Changes-not-Picked-Up-td3680479.html
>
> --
> View this message in context: http://grails.1312388.n4.nabble.com/reloading-of-static-files-in-Grails-1-4-0-M1-tp3616262p3683575.html
> Sent from the Grails - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>


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

   http://xircles.codehaus.org/manage_email

[virtualeyes]

To-date there's always some pain involved in working with Grails; this is offset by the immense power that this framework offers, so take the mostly good with the rare bad.

Try Rails and for sure as a new user you'll have many wtf moments; same for Django as well (although the auto-admin interface there is quite impressive, would absolutely love that in Grails)

Regardless, the fix here has me rolling again -- have to love 2.0 devel reloading, huge time saver compared to past versions...

[Paolo DiCanio]

virtualeyes wrote

To-date there's always some pain involved in working with Grails; this is offset by the immense power that this framework offers, so take the mostly good with the rare bad.

Elimiinating the bad seems like a better objective, particularly when it's easily achieved (as in this case).