Just go with the logical solution. If necessary, we can always make changes when we merge your patch.
-- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org Leo Mekenkamp wrote: > > Hi all, > > Bug http://jira.codehaus.org/browse/GRADLE-1295 is about gradle not > copying > empty directories. I found the reason for this bug: > the NormalizingCopySpecVisitor class explicitly excludes empty > directories. > Since NormalizingCopySpecVisitor is only used in CopyActionImpl, the > logical > solution for me would be to fix the code (and tests) and then issue a pull > request. > > However, since I am new here and unfamiliar with the politics surrounding > gradle development, there may be another way of handling bug fixes instead > of like this. For instance: leave NormalizingCopySpecVisitor as is and add > a > new class. I would like to fix this bug but I would also not like to > trample > on anyones toes. > > cheers, > --L > -- View this message in context: http://gradle.1045684.n5.nabble.com/no-empty-dir-in-copy-task-bug-tp4086152p4159592.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
