Have you tried convention mapping to the root spec?
https://github.com/gradle/gradle/blob/master/subprojects/core/src/main/groovy/org/gradle/api/tasks/AbstractCopyTask.java#L96-96
This is internal API, but you’re already in this hole with convention mappings.
On 22 August 2014 at 2:05:45 am, Peter Ledbrook (pe...@cacoethes.co.uk) wrote:
Hi,
I'm encountering a couple of occasions where I want to map the
properties of a plugin extension to the properties of a Zip task. This
works fine except for certain properties such as `excludes` and
`fileMode`. These are really properties on the underlying CopySpec and
that seems to cause the convention mapping issues.
I raised this as a question on the forums[1] but essentially
task.conventionMapping.map("excludes") {
project.extensions.lazybones.excludes
}
doesn't work if `task` is a Copy-derived task. Should this be
possible? If so, shall I raise a JIRA issue for it?
Thanks,
Peter
[1]:
http://forums.gradle.org/gradle/topics/how_do_i_map_a_plugins_extension_property_to_a_copy_tasks_excludes
--
Peter Ledbrook
t: @pledbrook
w: http://www.cacoethes.co.uk/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
