>
>
> On Aug 24, 2009, at 11:38 AM, Trond Andersen wrote:
>
> <snip>
>
> 4.) A project can define a default profile.
>> Should Gradle maybe use the same way as ConfigSlurper handles it? Outside
>> of the environment {...} is the default?
>>
>
> -1- url = 'x'
> -2- config/environment {
> -3- jdbcUrl = 'y'
> -4- dev { ... }
> -5- }
>
> I think the build/init.gradle context is already a default context (line
> 1).
The ConfigSlurper config file of course doesn't have this issue.
> line 3 is an equivalent location for doing this. People might decide to go
> for the line 3 approach, as it visually separates things. But functionality
> wise it shouldn't matter.
Agreed. Line 3 is seems the best option.
>
> How should we call the thing?
>
> Environment, Profiles, Configuration (to confuse people ;)) ?
>
Given that configuration is already used a lot this will probably confuse
people as you hint towards. Personally I've always considered this to be an
environment thing and internally in our team we always use this term.
Maven's profile term is a bit odd for me because I don't get
an association to environment or application configuration when using build
profile name, but then again - I'm not a CI/build master. This is a term
which Maven people to know and that is a pluss. The environment term might
also be misinterpret as OS environment more than application configuration.
Maybe a shorter version of application configuration could be applicable or
is application configuration too specific? Good terms and metaphors are
always difficult. Not much help here :-)
------ Trond
