I really don't remember exactly - I think when trying to replace the old
Resources task with Copy there was something that was using
Resources.getDestinationDir that was hard to get around. I didn't like it at
the time and think it definitely should be removed now. Having a single
destinationDir property (for the root copySpec) is wrong. It probably confuses
anything depending on that @OutputDirectory annotation too.
On 1/12/2010 6:47 AM, Hans Dockter wrote:
Hi Steve,
what is the purpose of having a distinct destination dir property of the
copy task, on top of the into property of the copy spec?
- Hans
--
Hans Dockter
Founder, Gradle
http://www.gradle.org, http://twitter.com/gradleorg
CEO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
