Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-RC1
-
Fix Version/s: 2.0-RC2
-
Component/s: None
-
Labels:None
Description
Problem reported on mailing list:
http://grails.1312388.n4.nabble.com/How-to-set-custom-environment-in-Grails2-0-0-RC1-interactive-mode-td3990393.html
tried
grails -Dgrails.env=foo
grails>shell
groovy:000> grails.util.Environment.current
===> DEVELOPMENTalso tried:
grails -Dgrails.env=foo
grails>shell -Dgrails.env=foo
groovy:000> grails.util.Environment.current
===> DEVELOPMENTgrails -Dgrails.env=foo
grails>-Dgrails.env=foo shell
groovy:000> grails.util.Environment.current
===> DEVELOPMENTSo is it possible to specify a custom environment for the interactive
mode or is this a bug?
Issue Links
- relates to
-
GRAILS-7433
wrong environment for war after selection from "did you mean list"
-
Fixed in 2.0.x and master branches. Cherry-picked
GRAILS-7433fix from master to 2.0.x before fixing because that contained changes to same file (DefaultCommandLine.java)