I've renamed it archivetaskpermissiontest as it didn't test the copy task at all.
Regards, René Gröschke @breskeby On 15.03.2012, at 18:13, Lars Hvile <[email protected]> wrote: > Where's the original integration test written for the copy-task's > permission handling? > > https://github.com/gradle/gradle/blob/53cabe6bba3d7961302decd5253f16b6c29aabb2/subprojects/integ-test/src/integTest/groovy/org/gradle/integtests/CopyTaskPermissionsIntegrationTest.groovy > > -- > Lars Hvile > > > On Thu, 2012-03-15 at 05:07 -0700, Rene Groeschke [via Gradle] wrote: > > > Hello Joern, > > I've updated the known issues section in the migration guide of > > milestone-9 (http://wiki.gradle.org/display/GRADLE/Gradle > > +1.0-milestone-9+Migration > > +Guide#Gradle1.0-milestone-9MigrationGuide-KnownIssues) and reopened > > http://issues.gradle.org/browse/GRADLE-971. Furthermore I've pushed a > > integration test > > ( > > https://github.com/gradle/gradle/commit/b3e2c2a88c1e786b76b8414388037ade63c0d549 > > ) for this. > > > > Thanks for pointing this out. A small hint for the next time: This > > kind of discussion/issue should be raised in the forum to discuss it > > there and not on the dev list. > > > > regards, > > René > > > > > > > > [hidden email] > > > 15. März 2012 11:25 > > > Hi Joern, > > > sorry, I've just checked the permissions of Lilith.app and not of > > > the JavaApplicationstub. Now I can reproduce your problem. Before > > > reopening a bug, give me some time to find out the details of the > > > problem. I'll ping you. > > > > > > regards, > > > rené > > > > > > > > > > > > > > > [hidden email] > > > 15. März 2012 10:10 > > > I just tried it again… > > > > > > > > > build/explodedApp/Lilith.app/Contents/MacOS/JavaApplicationStub > > > stays at 664 for me. > > > > > > > > > Did you remove the doLast workaround after forking? > > > The version in that commit contains a workaround for the problem. > > > You'd need to remove lines 604-608 in file > > > https://github.com/huxi/lilith/blob/6677657bb4c9ce710d3dd2a95d61fd97fd64f7e8/config.gradle > > > to reproduce the issue. > > > > > > > > > Cheers, > > > Joern. > > > > > > On 15.03.2012, at 00:01, Rene Groeschke wrote: > > > > > > > > > > > > > > > [hidden email] > > > 15. März 2012 00:01 > > > Hello Joern, > > > I've just forked your repo to reproduce this issue, but I am not > > > able to reproduce this error on my local machine. (macosx). After > > > running copyApp the filepermissions of the app file are set > > > correctly to 0755. > > > > > > regards, > > > René > > > > > > > > > > > > > > > > > > [hidden email] > > > 14. März 2012 23:18 > > > GRADLE-971, GRADLE-796 and GRADLE-673 are all reported as fixed in > > > m9. > > > > > > But if I remove the doLast-workaround at > > > https://github.com/huxi/lilith/blob/6677657bb4c9ce710d3dd2a95d61fd97fd64f7e8/config.gradle#L601 > > > the file does still have 644 instead of 755 as permission. > > > > > > I'm not sure how to proceed… should I reopen GRADLE-971 or should I > > > file a new bug for this problem? > > > > > > ------------------------------------------------------------ > > > Gradle 1.0-milestone-9 > > > ------------------------------------------------------------ > > > > > > Gradle build time: Tuesday, March 13, 2012 4:10:09 PM UTC > > > Groovy: 1.8.6 > > > Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010 > > > Ivy: 2.2.0 > > > JVM: 1.6.0_29 (Apple Inc. 20.4-b02-402) > > > OS: Mac OS X 10.7.3 x86_64 > > > > > > Or is there anything I'm missing? I assumed that this should be > > > fixed now. The tar task using the exact sam copyspec is working as > > > expected. > > > > > > Cheers, > > > Joern. > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe from this list, please visit: > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > > > > > > > > > [hidden email] > > > 13. März 2012 22:21 > > > The Gradle 1.0-milestone-9 is now available! > > > > > > > > > For the complete list of features and bug fixes take a look at > > > release notes here: http://wiki.gradle.org/display/GRADLE/Gradle > > > +1.0-milestone-9+Release+Notes. Please read the migration guide at > > > http://wiki.gradle.org/display/GRADLE/Gradle+1.0-milestone-9 > > > +Migration+Guide as there are some notable deprecations and > > > potential breaking changes. > > > > > > > > > You are just a quick update to gradle-wrapper.properties away from > > > checking out this new release. Your wrapper needs this: > > > http://services.gradle.org/distributions/gradle-1.0-milestone-9-bin.zip.. > > > > > > > > > Gradle 1.0-milestone-9 is planned to be the last milestone before we > > > go into the RC phase for 1.0 final. For more on the process from > > > here to 1.0 final, see > > > http://forums.gradle.org/gradle/topics/our_plan_for_gradle_1_0. > > > > > > > > > Cheers! > > > -- > > > Szczepan Faber > > > Principal engineer@gradleware > > > Lead@mockito > > > > > > ____________________________________________________________________ > > > > > > > > > > ______________________________________________________________________ > > If you reply to this email, your message will be added to the > > discussion below: > > http://gradle.1045684.n5.nabble.com/1-0-milestone-9-is-out-tp5562625p5567786.html > > > > To start a new topic under gradle-dev, email ml-node > > +[hidden email] > > To unsubscribe from gradle-dev, click here. > > NAML > > > View this message in context: Re: 1.0-milestone-9 is out! > Sent from the gradle-dev mailing list archive at Nabble.com.
