Re: Problem with gradle ...

I think Eclipse sometimes causes folders to be marked as read-only (can't find the reference). I had issues where I couldn't rebuild because the modules\javafx.base folder was read-only for some reason and I had to delete is manually. It would reoccur seemingly randomly. On Thu, Oct 31, 2019 at 4:

Re: Problem with gradle ...

Zitat von Nir Lisker : Seems like an OS level issue. I've not gotten this one yet. Could be a file lock, read-only file, user permissions config etc. yeah, for some reason the folder was write-protected .. removed for now, will dig later as to why it happened in the first place. Thanks

Re: Problem with gradle ...

Seems like an OS level issue. I've not gotten this one yet. Could be a file lock, read-only file, user permissions config etc. On Thu, Oct 31, 2019 at 4:24 PM Jeanette Winzenburg wrote: > > okay, now build everything went fine, but get an file access error > > > Task :controls:test FAILED > > FA

Re: Problem with gradle ...

okay, now build everything went fine, but get an file access error Task :controls:test FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':controls:test'. java.nio.file.AccessDeniedException: C:\Daten\data-for-work\eclipse\gitrep-openjdk\jfx-fork

Re: Problem with gradle ...

Zitat von Nir Lisker : Yes, the wrapper will know to download the correct version. I updated the build instructions page [1] to be more specific about the wrapper recently, and there is another update coming soon due to a problem I recently encountered with the buildsrc. Run ./gradlew from th

Re: Problem with gradle ...

Yes, the wrapper will know to download the correct version. I updated the build instructions page [1] to be more specific about the wrapper recently, and there is another update coming soon due to a problem I recently encountered with the buildsrc. Run ./gradlew from the root folder of the project

Re: Problem with gradle ...

The wrapper script works just like the gradle command but uses the gradle version specified by the project. See https://docs.gradle.org/current/userguide/gradle_wrapper.html > On Oct 31, 2019, at 9:58 AM, Jeanette Winzenburg > w

Re: Problem with gradle ...

Zitat von Nir Lisker : Did you run the wrapper with gradlew or just gradle? The latter uses the "global" version installed on the OS which might not be up to date (use 'gradle --version' to check). in my cygwin console I type: gradle and get the error message .. hmm ... so, yeah seems to

Re: Problem with gradle ...

If you are hitting this error, then you must have your own local installation on gradle. You can either update that local installation manually, or you can use "gradlew" which will always use the supported version of gradle: sh gradlew ... -- Kevin On 10/31/2019 6:41 AM, Jeanette Winzenbur

Re: Problem with gradle ...

Did you run the wrapper with gradlew or just gradle? The latter uses the "global" version installed on the OS which might not be up to date (use 'gradle --version' to check). - Nir On Thu, Oct 31, 2019 at 3:41 PM Jeanette Winzenburg wrote: > > .. fails (gradle run from cygwin console) with: > >

Re: Problem with gradle build

Hi Richard, On 10.7.2013 17:44, Richard Bair wrote: From this bug report it looks like the "depend" feature we have turned on by default is causing the problem. You can turn USE_DEPEND=false. This will cause your build times to become longer if you do all your builds from the command line. If

Re: Problem with gradle build

Good find! I see that this bug is most likely the issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=54090 From this bug report it looks like the "depend" feature we have turned on by default is causing the problem. You can turn USE_DEPEND=false. This will cause your build times to becom