War file creation in interactive mode

[Michael Berg-6]

C:\> grails war

 

...a war file is created with application.properties: grails.env=production set

 

C:\> grails interactive

Interactive mode ready, type your command name...

> war

 

...a war file is created with application.properties: grails.env=development set

 

Surely this is not intentional behaviour? Should a war file not always be for production use?

 

It certainly confused the heck out of me when I uploaded my war to the production server and it ran in development mode :-)

 

/Mike

 

 

[Graeme Rocher-2]

Yeh seems like a bug to me

Cheers

On Tue, Jul 8, 2008 at 8:57 AM, Michael Berg <michael.berg@...> wrote:

> C:\> grails war
>
> ...a war file is created with application.properties: grails.env=production
> set
>
> C:\> grails interactive
> Interactive mode ready, type your command name...
>> war
>
> ...a war file is created with application.properties: grails.env=development
> set
>
> Surely this is not intentional behaviour? Should a war file not always be
> for production use?
>
> It certainly confused the heck out of me when I uploaded my war to the
> production server and it ran in development mode :-)
>
> /Mike
>
>

--
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

[burtbeckwith]

I noticed something similar - running 'test' in interactive mode used the dev
datasource and blew away our dev data. We had recent backups but it took a
while to figure out what was going on.

Burt

On Tuesday 08 July 2008 4:01:43 am Graeme Rocher wrote:
> Yeh seems like a bug to me
>
> Cheers
>
> On Tue, Jul 8, 2008 at 8:57 AM, Michael Berg <michael.berg@...>
wrote:

> > C:\> grails war
> >
> > ...a war file is created with application.properties:
> > grails.env=production set
> >
> > C:\> grails interactive
> > Interactive mode ready, type your command name...
> >
> >> war
> >
> > ...a war file is created with application.properties:
> > grails.env=development set
> >
> > Surely this is not intentional behaviour? Should a war file not always be
> > for production use?
> >
> > It certainly confused the heck out of me when I uploaded my war to the
> > production server and it ran in development mode :-)
> >
> > /Mike

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

    http://xircles.codehaus.org/manage_email

[MikeHugo]

Already JIRA'd:  http://jira.codehaus.org/browse/GRAILS-2800

On Tue, Jul 8, 2008 at 5:45 AM, Burt Beckwith <burt@...> wrote:

I noticed something similar - running 'test' in interactive mode used the dev
datasource and blew away our dev data. We had recent backups but it took a
while to figure out what was going on.

Burt

On Tuesday 08 July 2008 4:01:43 am Graeme Rocher wrote:
> Yeh seems like a bug to me
>
> Cheers
>
> On Tue, Jul 8, 2008 at 8:57 AM, Michael Berg <michael.berg@...>
wrote:
> > C:\> grails war
> >
> > ...a war file is created with application.properties:
> > grails.env=production set
> >
> > C:\> grails interactive
> > Interactive mode ready, type your command name...
> >
> >> war
> >
> > ...a war file is created with application.properties:
> > grails.env=development set
> >
> > Surely this is not intentional behaviour? Should a war file not always be
> > for production use?
> >
> > It certainly confused the heck out of me when I uploaded my war to the
> > production server and it ran in development mode :-)
> >
> > /Mike

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

   http://xircles.codehaus.org/manage_email