An update: If i run from Powershell in the Project directory:
*PS C:\Development\myproject> ./gradlew --configure-on-demand -x check clean buildDownloading https://services.gradle.org/distributions/gradle-4.6-all.zip <https://services.gradle.org/distributions/gradle-4.6-all.zip>....* it starts downloading the Wrapper, and ./.gradle/wrapper/dists gets populated with gradle-4.6-all.zip as expected. Regards Jonathan On Sun, Mar 15, 2020 at 5:48 PM Jonathan Bergh <bergh.jonat...@gmail.com> wrote: > ok, thanks Lazlo, > > I have just cleared my ./.gradle/cache and ./.gradle/wrapper/dist > directories, set global Gradle options to Gradle 6.2.2 but Prefer gradle > wrapper. > > When i build my project, the output is: > > > > > > > > > > > > > > > > > > > > *JAVA_HOME="C:\Program Files\Java\jdk1.8.0_201"cd > C:\Development\myproject; ./gradlew --configure-on-demand -x check clean > buildConfiguration on demand is an incubating feature.> Task :clean> Task > :compileJavaNote: Some input files use unchecked or unsafe operations.Note: > Recompile with -Xlint:unchecked for details.> Task :processResources> Task > :classes> Task :jar> Task :assemble> Task :buildDeprecated Gradle features > were used in this build, making it incompatible with Gradle 7.0.Use > '--warning-mode all' to show the individual deprecation warnings.See > https://docs.gradle.org/6.2.2/userguide/command_line_interface.html#sec:command_line_warnings > <https://docs.gradle.org/6.2.2/userguide/command_line_interface.html#sec:command_line_warnings>BUILD > SUCCESSFUL in 5m 6s4 actionable tasks: 4 executed* > > When i check back in ./.gradle/wrapper/dists , there is only a 6.2.2 > installation, and cache also only has artifacts for 6.2.2 > > The project gradle wrapper (gradle-wrapper.properties) is: > > > > > *distributionBase=GRADLE_USER_HOMEdistributionPath=wrapper/distsdistributionUrl=https\://services.gradle.org/distributions/gradle-4.6-bin.zip > <http://services.gradle.org/distributions/gradle-4.6-bin.zip>zipStoreBase=GRADLE_USER_HOMEzipStorePath=wrapper/dists* > > So i am sure perhaps that Netbeans is not using the project gradle wrapper? > > Regards > Jonathan > > > > On Sun, Mar 15, 2020 at 5:00 PM Laszlo Kishalmi <laszlo.kisha...@gmail.com> > wrote: > >> Unfortunately attachments are not working in dev mailing list. You can >> share them some clipboarding site or you can create a JIRA issue on this >> and do the report there. >> >> Right now the wrapper detection checks the existence of >> gradle/wrapper/gradle-wrapper.properties in the root project. >> >> >> On 3/15/20 7:24 AM, Jonathan Bergh wrote: >> > Hi there, >> > >> > Just a quick question. We usually use Maven for build, for which >> > everything seems to work perfectly on NB11.3. However, we have a >> > project which uses Gradle for other reasons. >> > >> > When building on 11.3, via the IDE, i have "Use wrapper" set in global >> > IDE options but when i build (Clean Build) from the Project menu, >> > Netbeans seems to be using the globally configured Gradle >> > installation, rather than the Wrapper version? >> > >> > please see the attached. if i run from the command line, everything >> > builds fine, including finding the various plugins etc. >> > >> > Just wanted to check whether this was a real issue before logging. >> > Thanks a lot. >> > >> > Regards >> > Jon >> > gradle3.JPG >> > gradle2.JPG >> > gradle1.JPG >> >
