On 08/11/2011, at 1:32 AM, Luke Daley wrote:
> This doesn't compile:
>
> artifacts {
> default someZip
> }
>
> It needs to be:
>
> artifacts {
> delegate.default someZip
> }
Or artifacts { 'default' someZip }
>
> Given that now default does not extend archives, meaning that manually adding
> something to the default configuration is going to be likely, I think we need
> to rename this.
It depends on what its purpose is. If you want to add a jar to be used at
runtime, you'd simply add the jar to the runtime configuration.
I want to get rid of the idea of a default configuration at all. The (default)
configuration that is used by the consumer should instead be a function of what
the consumer is trying to do. If they're compiling java code, we should use
'api' (say). If they're running code on the jvm, we should use 'runtime'. If
they're assembling an ear, we should use 'ejbComponents'. And so on.
>
> We can probably do this in a backwards compatible way though by adding a
> configuration with a new name that extends “default”, and make “default” a
> special DeprecatedConfiguration that spits deprecated messages whenever
> something is added to it. Given that we can be backwards compatible, I think
> we should do this post 1.0.
>
> --
> Luke Daley
> Principal Engineer, Gradleware
> http://gradleware.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com
