Call for testing of Grails interactive mode
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Call for testing of Grails interactive mode
by Graeme Rocher-2
::
Rate this Message:
Hi all,
I've committed the first cut of an interactive mode for Grails that lets Grails keep the JVM running for commands like create-*, generate-* and test-app. One of the real benefits is that as the JVM's JIT inlines code things to start to run faster and faster So for example in my tests the first time I ran my suite for unit and integration tests it took 26s but after 2 or 3 runs it was down to 8s. Also you can run commands whilst Grails is actually running (ie run-app) Anyway there are probably many bugs and oversights that we haven't thought about so some user testing would be appreciated. As the codehaus build server is down for a few days you will need to checkout and build Grails from sources Regards -- Graeme Rocher Grails Project Lead G2One, Inc. Chief Technology Officer http://www.g2one.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Call for testing of Grails interactive mode
by Graeme Rocher-2
::
Rate this Message:
Oh btw to load interactive mode type:
grails interactive Cheers On Tue, Apr 8, 2008 at 11:43 AM, Graeme Rocher <graeme@...> wrote: > Hi all, > > I've committed the first cut of an interactive mode for Grails that > lets Grails keep the JVM running for commands like create-*, > generate-* and test-app. One of the real benefits is that as the JVM's > JIT inlines code things to start to run faster and faster > > So for example in my tests the first time I ran my suite for unit and > integration tests it took 26s but after 2 or 3 runs it was down to 8s. > Also you can run commands whilst Grails is actually running (ie > run-app) > > Anyway there are probably many bugs and oversights that we haven't > thought about so some user testing would be appreciated. As the > codehaus build server is down for a few days you will need to checkout > and build Grails from sources > > Regards > > -- > Graeme Rocher > Grails Project Lead > G2One, Inc. Chief Technology Officer > http://www.g2one.com > -- Graeme Rocher Grails Project Lead G2One, Inc. Chief Technology Officer http://www.g2one.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Re: Call for testing of Grails interactive mode
by MikeHugo
::
Rate this Message:
I got the latest grails code from SVN, typed ant jar (to build
Grails), upgraded my project and then: grails interactive test-app But before it gets to running the tests, I get the following exception: org.codehaus.groovy.grails.plugins.exceptions.PluginException: Plugin [mimeTypes:1.0] must specify a version. eg: def version = 0.1 at Package_groovy$_run_closure5_closure22.doCall(Package_groovy:223) at Package_groovy$_run_closure5_closure22.doCall(Package_groovy) at Init_groovy$_run_closure6.doCall(Init_groovy:128) at Package_groovy$_run_closure5.doCall(Package_groovy:221) at Package_groovy$_run_closure5.doCall(Package_groovy) at Package_groovy$_run_closure3.doCall(Package_groovy:149) at Package_groovy$_run_closure3.doCall(Package_groovy) at TestApp_groovy$_run_closure3.doCall(TestApp_groovy:90) at TestApp_groovy$_run_closure3.doCall(TestApp_groovy) at TestApp_groovy$_run_closure1.doCall(TestApp_groovy:63) at TestApp_groovy$_run_closure1.doCall(TestApp_groovy) at gant.Gant.dispatch(Gant.groovy:271) at gant.Gant.this$2$dispatch(Gant.groovy) at gant.Gant.invokeMethod(Gant.groovy) at gant.Gant.processTargets(Gant.groovy:436) at gant.Gant.processArgs(Gant.groovy:372) This may not be a problem with "grails interactive" since if I just run "grails test-app" I get the same problem. Mike On Apr 8, 2008, at 5:44 AM, Graeme Rocher wrote: > Oh btw to load interactive mode type: > > grails interactive > > Cheers > > On Tue, Apr 8, 2008 at 11:43 AM, Graeme Rocher <graeme@...> > wrote: >> Hi all, >> >> I've committed the first cut of an interactive mode for Grails that >> lets Grails keep the JVM running for commands like create-*, >> generate-* and test-app. One of the real benefits is that as the >> JVM's >> JIT inlines code things to start to run faster and faster >> >> So for example in my tests the first time I ran my suite for unit and >> integration tests it took 26s but after 2 or 3 runs it was down to >> 8s. >> Also you can run commands whilst Grails is actually running (ie >> run-app) >> >> Anyway there are probably many bugs and oversights that we haven't >> thought about so some user testing would be appreciated. As the >> codehaus build server is down for a few days you will need to >> checkout >> and build Grails from sources >> >> Regards >> >> -- >> Graeme Rocher >> Grails Project Lead >> G2One, Inc. Chief Technology Officer >> http://www.g2one.com >> > > > > -- > Graeme Rocher > Grails Project Lead > G2One, Inc. Chief Technology Officer > http://www.g2one.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 |
|
|
Re: Re: Call for testing of Grails interactive mode
by Graeme Rocher-2
::
Rate this Message:
Hmm I've had similar problems when I've had intellij open and its
overrode my classes with stubs in which case I had to do an ant clean jar Cheers On Tue, Apr 8, 2008 at 1:23 PM, Mike Hugo <mike@...> wrote: > I got the latest grails code from SVN, typed ant jar (to build Grails), > upgraded my project and then: > grails interactive > test-app > > But before it gets to running the tests, I get the following exception: > > org.codehaus.groovy.grails.plugins.exceptions.PluginException: Plugin > [mimeTypes:1.0] must specify a version. eg: def version = 0.1 > at Package_groovy$_run_closure5_closure22.doCall(Package_groovy:223) > at Package_groovy$_run_closure5_closure22.doCall(Package_groovy) > at Init_groovy$_run_closure6.doCall(Init_groovy:128) > at Package_groovy$_run_closure5.doCall(Package_groovy:221) > at Package_groovy$_run_closure5.doCall(Package_groovy) > at Package_groovy$_run_closure3.doCall(Package_groovy:149) > at Package_groovy$_run_closure3.doCall(Package_groovy) > at TestApp_groovy$_run_closure3.doCall(TestApp_groovy:90) > at TestApp_groovy$_run_closure3.doCall(TestApp_groovy) > at TestApp_groovy$_run_closure1.doCall(TestApp_groovy:63) > at TestApp_groovy$_run_closure1.doCall(TestApp_groovy) > at gant.Gant.dispatch(Gant.groovy:271) > at gant.Gant.this$2$dispatch(Gant.groovy) > at gant.Gant.invokeMethod(Gant.groovy) > at gant.Gant.processTargets(Gant.groovy:436) > at gant.Gant.processArgs(Gant.groovy:372) > > This may not be a problem with "grails interactive" since if I just run > "grails test-app" I get the same problem. > > Mike > > > > On Apr 8, 2008, at 5:44 AM, Graeme Rocher wrote: > > > > > > > > > > Oh btw to load interactive mode type: > > > > grails interactive > > > > Cheers > > > > On Tue, Apr 8, 2008 at 11:43 AM, Graeme Rocher <graeme@...> wrote: > > > > > Hi all, > > > > > > I've committed the first cut of an interactive mode for Grails that > > > lets Grails keep the JVM running for commands like create-*, > > > generate-* and test-app. One of the real benefits is that as the JVM's > > > JIT inlines code things to start to run faster and faster > > > > > > So for example in my tests the first time I ran my suite for unit and > > > integration tests it took 26s but after 2 or 3 runs it was down to 8s. > > > Also you can run commands whilst Grails is actually running (ie > > > run-app) > > > > > > Anyway there are probably many bugs and oversights that we haven't > > > thought about so some user testing would be appreciated. As the > > > codehaus build server is down for a few days you will need to checkout > > > and build Grails from sources > > > > > > Regards > > > > > > -- > > > Graeme Rocher > > > Grails Project Lead > > > G2One, Inc. Chief Technology Officer > > > http://www.g2one.com > > > > > > > > > > > > > > -- > > Graeme Rocher > > Grails Project Lead > > G2One, Inc. Chief Technology Officer > > http://www.g2one.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 > > > -- Graeme Rocher Grails Project Lead G2One, Inc. Chief Technology Officer http://www.g2one.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Re: Call for testing of Grails interactive mode
by MikeHugo
::
Rate this Message:
Thanks, that solved the problem. So far so good, I'll keep using it
and post any feedback. Mike On Apr 8, 2008, at 7:31 AM, Graeme Rocher wrote: > Hmm I've had similar problems when I've had intellij open and its > overrode my classes with stubs in which case I had to do an > > ant clean jar > > Cheers > > On Tue, Apr 8, 2008 at 1:23 PM, Mike Hugo <mike@...> wrote: >> I got the latest grails code from SVN, typed ant jar (to build >> Grails), >> upgraded my project and then: >> grails interactive >> test-app >> >> But before it gets to running the tests, I get the following >> exception: >> >> org.codehaus.groovy.grails.plugins.exceptions.PluginException: Plugin >> [mimeTypes:1.0] must specify a version. eg: def version = 0.1 >> at Package_groovy >> $_run_closure5_closure22.doCall(Package_groovy:223) >> at Package_groovy >> $_run_closure5_closure22.doCall(Package_groovy) >> at Init_groovy$_run_closure6.doCall(Init_groovy:128) >> at Package_groovy$_run_closure5.doCall(Package_groovy:221) >> at Package_groovy$_run_closure5.doCall(Package_groovy) >> at Package_groovy$_run_closure3.doCall(Package_groovy:149) >> at Package_groovy$_run_closure3.doCall(Package_groovy) >> at TestApp_groovy$_run_closure3.doCall(TestApp_groovy:90) >> at TestApp_groovy$_run_closure3.doCall(TestApp_groovy) >> at TestApp_groovy$_run_closure1.doCall(TestApp_groovy:63) >> at TestApp_groovy$_run_closure1.doCall(TestApp_groovy) >> at gant.Gant.dispatch(Gant.groovy:271) >> at gant.Gant.this$2$dispatch(Gant.groovy) >> at gant.Gant.invokeMethod(Gant.groovy) >> at gant.Gant.processTargets(Gant.groovy:436) >> at gant.Gant.processArgs(Gant.groovy:372) >> >> This may not be a problem with "grails interactive" since if I just >> run >> "grails test-app" I get the same problem. >> >> Mike >> >> >> >> On Apr 8, 2008, at 5:44 AM, Graeme Rocher wrote: >> >> >>> >>> >>> >>> Oh btw to load interactive mode type: >>> >>> grails interactive >>> >>> Cheers >>> >>> On Tue, Apr 8, 2008 at 11:43 AM, Graeme Rocher <graeme@...> >>> wrote: >>> >>>> Hi all, >>>> >>>> I've committed the first cut of an interactive mode for Grails that >>>> lets Grails keep the JVM running for commands like create-*, >>>> generate-* and test-app. One of the real benefits is that as the >>>> JVM's >>>> JIT inlines code things to start to run faster and faster >>>> >>>> So for example in my tests the first time I ran my suite for unit >>>> and >>>> integration tests it took 26s but after 2 or 3 runs it was down >>>> to 8s. >>>> Also you can run commands whilst Grails is actually running (ie >>>> run-app) >>>> >>>> Anyway there are probably many bugs and oversights that we haven't >>>> thought about so some user testing would be appreciated. As the >>>> codehaus build server is down for a few days you will need to >>>> checkout >>>> and build Grails from sources >>>> >>>> Regards >>>> >>>> -- >>>> Graeme Rocher >>>> Grails Project Lead >>>> G2One, Inc. Chief Technology Officer >>>> http://www.g2one.com >>>> >>>> >>> >>> >>> >>> -- >>> Graeme Rocher >>> Grails Project Lead >>> G2One, Inc. Chief Technology Officer >>> http://www.g2one.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 >> >> >> > > > > -- > Graeme Rocher > Grails Project Lead > G2One, Inc. Chief Technology Officer > http://www.g2one.com > > - --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Re: Call for testing of Grails interactive mode
by fernando.takai
::
Rate this Message:
As for the issues, do we open jiras for them, or just email to this thread?
On Tue, Apr 8, 2008 at 11:27 AM, Mike Hugo <mike@...> wrote: Thanks, that solved the problem. So far so good, I'll keep using it and post any feedback. -- Fernando "Takai" http://flickr.com/photos/supeertakai http://fernandotakai.tumblr.com/ http://twitter.com/fernando_takai |
|
|
Re: Re: Call for testing of Grails interactive mode
by Graeme Rocher-2
::
Rate this Message:
JIRAs are good
Cheers On Tue, Apr 8, 2008 at 4:13 PM, Fernando <fernando.takai@...> wrote: > As for the issues, do we open jiras for them, or just email to this thread? > > > > On Tue, Apr 8, 2008 at 11:27 AM, Mike Hugo <mike@...> wrote: > > > Thanks, that solved the problem. So far so good, I'll keep using it and > post any feedback. > > > > Mike > > > > > > > > > > On Apr 8, 2008, at 7:31 AM, Graeme Rocher wrote: > > > > > > > Hmm I've had similar problems when I've had intellij open and its > > > overrode my classes with stubs in which case I had to do an > > > > > > ant clean jar > > > > > > Cheers > > > > > > On Tue, Apr 8, 2008 at 1:23 PM, Mike Hugo <mike@...> wrote: > > > > > > > I got the latest grails code from SVN, typed ant jar (to build > Grails), > > > > upgraded my project and then: > > > > grails interactive > > > > test-app > > > > > > > > But before it gets to running the tests, I get the following > exception: > > > > > > > > org.codehaus.groovy.grails.plugins.exceptions.PluginException: Plugin > > > > [mimeTypes:1.0] must specify a version. eg: def version = 0.1 > > > > at > Package_groovy$_run_closure5_closure22.doCall(Package_groovy:223) > > > > at Package_groovy$_run_closure5_closure22.doCall(Package_groovy) > > > > at Init_groovy$_run_closure6.doCall(Init_groovy:128) > > > > at Package_groovy$_run_closure5.doCall(Package_groovy:221) > > > > at Package_groovy$_run_closure5.doCall(Package_groovy) > > > > at Package_groovy$_run_closure3.doCall(Package_groovy:149) > > > > at Package_groovy$_run_closure3.doCall(Package_groovy) > > > > at TestApp_groovy$_run_closure3.doCall(TestApp_groovy:90) > > > > at TestApp_groovy$_run_closure3.doCall(TestApp_groovy) > > > > at TestApp_groovy$_run_closure1.doCall(TestApp_groovy:63) > > > > at TestApp_groovy$_run_closure1.doCall(TestApp_groovy) > > > > at gant.Gant.dispatch(Gant.groovy:271) > > > > at gant.Gant.this$2$dispatch(Gant.groovy) > > > > at gant.Gant.invokeMethod(Gant.groovy) > > > > at gant.Gant.processTargets(Gant.groovy:436) > > > > at gant.Gant.processArgs(Gant.groovy:372) > > > > > > > > This may not be a problem with "grails interactive" since if I just > run > > > > "grails test-app" I get the same problem. > > > > > > > > Mike > > > > > > > > > > > > > > > > On Apr 8, 2008, at 5:44 AM, Graeme Rocher wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Oh btw to load interactive mode type: > > > > > > > > > > grails interactive > > > > > > > > > > Cheers > > > > > > > > > > On Tue, Apr 8, 2008 at 11:43 AM, Graeme Rocher <graeme@...> > wrote: > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > I've committed the first cut of an interactive mode for Grails > that > > > > > > lets Grails keep the JVM running for commands like create-*, > > > > > > generate-* and test-app. One of the real benefits is that as the > JVM's > > > > > > JIT inlines code things to start to run faster and faster > > > > > > > > > > > > So for example in my tests the first time I ran my suite for unit > and > > > > > > integration tests it took 26s but after 2 or 3 runs it was down to > 8s. > > > > > > Also you can run commands whilst Grails is actually running (ie > > > > > > run-app) > > > > > > > > > > > > Anyway there are probably many bugs and oversights that we haven't > > > > > > thought about so some user testing would be appreciated. As the > > > > > > codehaus build server is down for a few days you will need to > checkout > > > > > > and build Grails from sources > > > > > > > > > > > > Regards > > > > > > > > > > > > -- > > > > > > Graeme Rocher > > > > > > Grails Project Lead > > > > > > G2One, Inc. Chief Technology Officer > > > > > > http://www.g2one.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Graeme Rocher > > > > > Grails Project Lead > > > > > G2One, Inc. Chief Technology Officer > > > > > http://www.g2one.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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Graeme Rocher > > > Grails Project Lead > > > G2One, Inc. Chief Technology Officer > > > http://www.g2one.com > > > > > > - > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > -- > Fernando "Takai" > http://flickr.com/photos/supeertakai > http://fernandotakai.tumblr.com/ > http://twitter.com/fernando_takai -- Graeme Rocher Grails Project Lead G2One, Inc. Chief Technology Officer http://www.g2one.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Call for testing of Grails interactive mode
by Peter Ledbrook-2
::
Rate this Message:
> Anyway there are probably many bugs and oversights that we haven't
> thought about so some user testing would be appreciated. As the > codehaus build server is down for a few days you will need to checkout > and build Grails from sources Can't do: run-app -Dserver.port=9090 Works if you do: grails -Dserver.port=9090 interactive run-app One option, I guess, would be to have interactive's script launcher use System.setProperty() for any "-D*" parameters. Cheers, Peter -- Software Engineer G2One, Inc. http://www.g2one.com/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
