hi adam,
i guess the repo-interference/mixin can be
implemented in many ways ...
something that came to my mind:
[excuse me, if this is stupid, i still know very
few about gradle internals]
1. the call to myRepositoryChain() in the
repositories-closure triggers missing-method
2. a placeholder for myRepositoryChain is inserted
into the repository-container
3. an event is fired to notify plugins
4. plugins that listen to this kind of event
can modify the repository-chain esp. by
exchanging or updating the placeholder(s).
5. check if the placeholder(s) are processed
as expected
grüsse
Adam Murdoch-2 wrote:
>
> It will be. The maven plugin will (probably) be using this to add the
> mavenInstaller() and mavenDeployer() methods.
>
> You will be able to add properties and methods to RepositoryHandler
> using either a convention object, or a closure:
>
> // Using a convention object
> repositories.convention.plugins.myPlugin = new MyConventionObject()
>
> class MyConventionObject {
> def myRepositoryChain() { ... }
>
> ... maybe some other properties and methods ...
> }
>
> // Using a closure
>
> repositories.myRepositoryChain = { -> ... }
>
--
View this message in context:
http://old.nabble.com/customize-gradle-dsl-for-adding-my-repository%28-chain%29---tp26636162p26657191.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
