On 27/09/2011, at 9:42 PM, Carlton Brown wrote: > What are the other ways? I don't mind regex when necessary,
http://www.gradle.org/releases/1.0-milestone-4/docs/dsl/org.gradle.api.tasks.Copy.html#org.gradle.api.tasks.Copy:rename(groovy.lang.Closure) You can give rename a closure and cut the name up however you like. > and I know that duplicating ivy is not the goal of this project, but it would > really make sense to have a more specialized abstraction for dealing with > artifacts than just treating them as undifferentiated files. That's proven to be not a very common need, and this kind of abstraction makes using different kinds of artifacts and artifact sources possible. It's also not about not duplicating Ivy, it's about being a more general tool. Ivy is an implementation detail and over time less Ivy-isms will be at the surface. I think what you might be after is a way to create a kind of mini repository locally inside your build. Most users never need to do this but it does pop up sometimes. At the moment there is no easy way to do this in a way that includes all the metadata. It is easy to do for just the artifacts though. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
