Best way to reload changes?

[mtyson]

Hey Guys,

Veteran Java dev here, new to (and excited about) Grails.

Right now, I make changes, then stop the server and execute run-app.  Is there a better (quicker/one-step) way to get the changes deployed?

I'm using Spring STS (but I'm familiar with the commandline stuff also).

Thanks,

Matt Tyson

[asinesio]

You don't have to stop the server with 95% of your changes.  Run-app uses a custom classloader that checks for changes as long as you're in the "development" environment (the default).

Domain changes will clear the in memory database and some plugins don't refresh their configuration properly, but otherwise you can just change, save, and reload the page.  Services, controllers, GSPs, Taglibs, and most other objects reload without issue.

Andy

On Jun 16, 2012, at 10:52 AM, Matthew Tyson wrote:

> Hey Guys,
>
> Veteran Java dev here, new to (and excited about) Grails.
>
> Right now, I make changes, then stop the server and execute run-app.  Is there a better (quicker/one-step) way to get the changes deployed?
>
> I'm using Spring STS (but I'm familiar with the commandline stuff also).
>
> Thanks,
>
> Matt Tyson

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

    http://xircles.codehaus.org/manage_email

[longwa]

If you aren't getting class reloading in development mode, there are some bugs with the command line processing that can cause the reloading agent to not be included.

Check the command line for the java process and make sure you see -javaagent as one of the options. If not, you won't get the active reloading. Some editors (Intellij, for one) can cause the reloading agent to be ignored in certain cases.

On Sat, Jun 16, 2012 at 12:37 PM, Andy Sinesio <[hidden email]> wrote:

You don't have to stop the server with 95% of your changes.  Run-app uses a custom classloader that checks for changes as long as you're in the "development" environment (the default).

Domain changes will clear the in memory database and some plugins don't refresh their configuration properly, but otherwise you can just change, save, and reload the page.  Services, controllers, GSPs, Taglibs, and most other objects reload without issue.

Andy

On Jun 16, 2012, at 10:52 AM, Matthew Tyson wrote:

> Hey Guys,
>
> Veteran Java dev here, new to (and excited about) Grails.
>
> Right now, I make changes, then stop the server and execute run-app.  Is there a better (quicker/one-step) way to get the changes deployed?
>
> I'm using Spring STS (but I'm familiar with the commandline stuff also).
>
> Thanks,
>
> Matt Tyson

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

   http://xircles.codehaus.org/manage_email

[mtyson]

Thanks you guys.  You are absolutely right.  run-app is auto-loading the changes.  Never stopped to think it was that simple.

Best,

Matt Tyson

On Sat, Jun 16, 2012 at 9:18 AM, Aaron Long <[hidden email]> wrote:

If you aren't getting class reloading in development mode, there are some bugs with the command line processing that can cause the reloading agent to not be included.

Check the command line for the java process and make sure you see -javaagent as one of the options. If not, you won't get the active reloading. Some editors (Intellij, for one) can cause the reloading agent to be ignored in certain cases.

On Sat, Jun 16, 2012 at 12:37 PM, Andy Sinesio <[hidden email]> wrote:

You don't have to stop the server with 95% of your changes.  Run-app uses a custom classloader that checks for changes as long as you're in the "development" environment (the default).

Domain changes will clear the in memory database and some plugins don't refresh their configuration properly, but otherwise you can just change, save, and reload the page.  Services, controllers, GSPs, Taglibs, and most other objects reload without issue.

Andy

On Jun 16, 2012, at 10:52 AM, Matthew Tyson wrote:

> Hey Guys,
>
> Veteran Java dev here, new to (and excited about) Grails.
>
> Right now, I make changes, then stop the server and execute run-app.  Is there a better (quicker/one-step) way to get the changes deployed?
>
> I'm using Spring STS (but I'm familiar with the commandline stuff also).
>
> Thanks,
>
> Matt Tyson

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

   http://xircles.codehaus.org/manage_email