On Aug 24, 2009, at 7:37 PM, John Murph wrote:
On Mon, Aug 24, 2009 at 7:18 AM, Trond Andersen <[email protected]
> wrote:
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 :-)
In my mind, this is an execution profile. Like Trond suggested,
environment is a bit overused and generic. Configuration is also
overused (at least by Gradle), so it's out as well.
We are still pre 1.0 and I grow more and more unhappy with the term
configuration for something which is usually a classpath. I just took
this term from Ivy because I couldn't think of anything better. But I
think we should try hard to find a better name. Then 'configuration'
would be free.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
