Thanks Taher,
That sounds like a good news. I indeed did not cross any issue by commenting out the content of the cleanGradle task
About the cleanAnt, I think we can indeed remove it now that it's in the R16.11.
I'll remove both in a few days if nobody complains
Jacques
Le 14/01/2017 à 17:44, Taher Alkhateeb a écrit :
> Hi Jacques,
>
> My suspicion is that the upgrade to gradle 3+ (which automatically starts
> the daemon) leads to locking the above mentioned file and hence the problem
> that you're facing.
>
> I think it is safe to remove cleanGradle and also while we are at it
> cleanAnt tasks from build.gradle
>
>
>
> On Sat, Jan 14, 2017 at 4:14 PM, Jacques Le Roux <
>
[hidden email]> wrote:
>
>> Hi,
>>
>> It's now 2 weeks that I need to comment out the cleanGradle task even on a
>> fresh checked out working copy (named ofbizCleanGradle), else I get
>>
>> C:\projectsASF\ofbizCleanGradle>svn st
>> C:\projectsASF\ofbizCleanGradle>
>>
>> C:\projectsASF\ofbizCleanGradle>gradlew cleanGradle
>> :cleanGradle FAILED
>> FAILURE: Build failed with an exception.
>>
>> * Where:Build file 'C:\projectsASF\ofbizCleanGradle\build.gradle' line:
>> 769
>> * What went wrong:Execution failed for task ':cleanGradle'.
>>> Unable to delete file: C:\projectsASF\ofbizCleanGradl
>> e\.gradle\3.2.1\taskArtifacts\taskArtifacts.lock
>> * Try:Run with --stacktrace option to get the stack trace. Run with --info
>> or --debug option to get more log output.
>>
>> BUILD FAILED
>> Total time: 7.73 secs
>>
>> I wonder if I'm the only one getting that. Maybe because I'm the only one
>> using Windows? I have indeed any issues when running the same locally in
>> Ubuntu (in VirtualBox) nor on demos in VM2 (Debian).
>> The weird part is I can't find anything when Googling for
>> "taskArtifacts.lock" windows but a Chinese article which says nothing about
>> my issue (Google translation).
>>
>> Jacques
>>
>>
Locked
