On 12 September 2011 01:01, Adam Murdoch <[email protected]> wrote:
> One question is whether instead of having the url add some default patterns,
> we go straight to the layout based approach, with 3 fixed layout
> implementations for now: Maven, Gradle Ivy, and pattern based? I think this
> will help us move towards the fuller DSL later in a backwards-compatible
> way, and means we don't have to expose things like the m2compatible flag on
> our DSL, but can still handle that use case.
I like this idea, and I've started down this track. Here's my tentative DSL:
ivy {
url = 'http://host'
layout 'gradle' // this is the default
}
ivy {
url = 'build/repo'
layout 'maven' // uses same pattern as gradle, but replaces '.'
with '/' in organisation
// Can still add additional artifacts and ivy patterns
artifactPattern 'http://other/[module]/[artifact].[ext]
ivyPattern 'http://other/[module]/ivy.xml'
}
ivy {
url = 'build/repo'
layout 'pattern', {
artifacts '[organisation]/[module]/...'
artifacts '[other]'
ivy 'ivy pattern'
}
}
Thoughts?
Daz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
