Gradle loadDefault has some hiccup on BuildBot

[Jacques Le Roux]

HI,

https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps/shell/logs/stdio

https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps/shell/logs/stdio

All is OK locally (here at least), so I guess better to wait and see. Could though be that the error is everywhere, I don't want to swipe my Gradle
cache to verify!

This shows that you should not rely on Gradle in production. I more and more believe Pierre is right on this aspect!

Jacques

[taher]

Jacques, this has nothing to do with stability. Something is wrong in the
configuration. The error message shows it clearly:

* What went wrong: Task 'loadDefault' not found in root project 'build'.

On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]>
wrote:

> HI,
>
> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/
> steps/shell/logs/stdio
>
> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/
> steps/shell/logs/stdio
>
> All is OK locally (here at least), so I guess better to wait and see.
> Could though be that the error is everywhere, I don't want to swipe my
> Gradle cache to verify!
>
> This shows that you should not rely on Gradle in production. I more and
> more believe Pierre is right on this aspect!
>
> Jacques
>
>

[taher]

I would also like to add that massive production systems are deployed on
Gradle already. Our issues are familiarity, not stability.

On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]>
wrote:

> Jacques, this has nothing to do with stability. Something is wrong in the
> configuration. The error message shows it clearly:
>
> * What went wrong: Task 'loadDefault' not found in root project 'build'.
>
> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]>
> wrote:
>
>> HI,
>>
>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>> /shell/logs/stdio
>>
>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>> /shell/logs/stdio
>>
>> All is OK locally (here at least), so I guess better to wait and see.
>> Could though be that the error is everywhere, I don't want to swipe my
>> Gradle cache to verify!
>>
>> This shows that you should not rely on Gradle in production. I more and
>> more believe Pierre is right on this aspect!
>>
>> Jacques
>>
>>

[taher]

I also checked the second log, we have an issue with one of the
dependencies on Shiro. Needs a little digging through but this is an issue
you'd face regardless of the build system as it has to do with the remote
repository.

On Aug 6, 2016 10:11 AM, "Taher Alkhateeb" <[hidden email]>
wrote:

> I would also like to add that massive production systems are deployed on
> Gradle already. Our issues are familiarity, not stability.
>
> On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]>
> wrote:
>
>> Jacques, this has nothing to do with stability. Something is wrong in the
>> configuration. The error message shows it clearly:
>>
>> * What went wrong: Task 'loadDefault' not found in root project 'build'.
>>
>> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]>
>> wrote:
>>
>>> HI,
>>>
>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>>> /shell/logs/stdio
>>>
>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>>> /shell/logs/stdio
>>>
>>> All is OK locally (here at least), so I guess better to wait and see.
>>> Could though be that the error is everywhere, I don't want to swipe my
>>> Gradle cache to verify!
>>>
>>> This shows that you should not rely on Gradle in production. I more and
>>> more believe Pierre is right on this aspect!
>>>
>>> Jacques
>>>
>>>

[Jacques Le Roux]

Seems that you were too fast, see the second link please

Jacques


Le 06/08/2016 à 11:10, Taher Alkhateeb a écrit :

> Jacques, this has nothing to do with stability. Something is wrong in the
> configuration. The error message shows it clearly:
>
> * What went wrong: Task 'loadDefault' not found in root project 'build'.
>
> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]>
> wrote:
>
>> HI,
>>
>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/
>> steps/shell/logs/stdio
>>
>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/
>> steps/shell/logs/stdio
>>
>> All is OK locally (here at least), so I guess better to wait and see.
>> Could though be that the error is everywhere, I don't want to swipe my
>> Gradle cache to verify!
>>
>> This shows that you should not rely on Gradle in production. I more and
>> more believe Pierre is right on this aspect!
>>
>> Jacques
>>
>>

[Jacques Le Roux]

I totally agree, that's why I'll never rely on Gradle in production

Jacques


Le 06/08/2016 à 11:15, Taher Alkhateeb a écrit :

> I also checked the second log, we have an issue with one of the
> dependencies on Shiro. Needs a little digging through but this is an issue
> you'd face regardless of the build system as it has to do with the remote
> repository.
>
> On Aug 6, 2016 10:11 AM, "Taher Alkhateeb" <[hidden email]>
> wrote:
>
>> I would also like to add that massive production systems are deployed on
>> Gradle already. Our issues are familiarity, not stability.
>>
>> On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]>
>> wrote:
>>
>>> Jacques, this has nothing to do with stability. Something is wrong in the
>>> configuration. The error message shows it clearly:
>>>
>>> * What went wrong: Task 'loadDefault' not found in root project 'build'.
>>>
>>> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]>
>>> wrote:
>>>
>>>> HI,
>>>>
>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>>>> /shell/logs/stdio
>>>>
>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>>>> /shell/logs/stdio
>>>>
>>>> All is OK locally (here at least), so I guess better to wait and see.
>>>> Could though be that the error is everywhere, I don't want to swipe my
>>>> Gradle cache to verify!
>>>>
>>>> This shows that you should not rely on Gradle in production. I more and
>>>> more believe Pierre is right on this aspect!
>>>>
>>>> Jacques
>>>>
>>>>

[taher]

Hi Jacques,

I guess then you mean you never rely on a remote repository for production,
Gradle is responsible for fetching, it is the repository that matters. This
is an area where fine-tuning of the selected libraries is important rather
than dropping down to java -jar.

Taher Alkhateeb

On Sat, Aug 6, 2016 at 12:28 PM, Jacques Le Roux <
[hidden email]> wrote:

> I totally agree, that's why I'll never rely on Gradle in production
>
> Jacques
>
>
> Le 06/08/2016 à 11:15, Taher Alkhateeb a écrit :
>
>> I also checked the second log, we have an issue with one of the
>> dependencies on Shiro. Needs a little digging through but this is an issue
>> you'd face regardless of the build system as it has to do with the remote
>> repository.
>>
>> On Aug 6, 2016 10:11 AM, "Taher Alkhateeb" <[hidden email]>
>> wrote:
>>
>> I would also like to add that massive production systems are deployed on
>>> Gradle already. Our issues are familiarity, not stability.
>>>
>>> On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]>
>>> wrote:
>>>
>>> Jacques, this has nothing to do with stability. Something is wrong in the
>>>> configuration. The error message shows it clearly:
>>>>
>>>> * What went wrong: Task 'loadDefault' not found in root project 'build'.
>>>>
>>>> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]
>>>> >
>>>> wrote:
>>>>
>>>> HI,
>>>>>
>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>>>>> /shell/logs/stdio
>>>>>
>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>>>>> /shell/logs/stdio
>>>>>
>>>>> All is OK locally (here at least), so I guess better to wait and see.
>>>>> Could though be that the error is everywhere, I don't want to swipe my
>>>>> Gradle cache to verify!
>>>>>
>>>>> This shows that you should not rely on Gradle in production. I more and
>>>>> more believe Pierre is right on this aspect!
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>

[Jacques Le Roux]

Yes that's a better to way to say it, thanks.

Indeed having collected and checked (I think at OWASP dependency checker) the libs and then stored them in a specific place seems a good way to go.

I don't see much differences with java -jar. Where is it easier?

Jacques


Le 06/08/2016 à 11:30, Taher Alkhateeb a écrit :

> Hi Jacques,
>
> I guess then you mean you never rely on a remote repository for production,
> Gradle is responsible for fetching, it is the repository that matters. This
> is an area where fine-tuning of the selected libraries is important rather
> than dropping down to java -jar.
>
> Taher Alkhateeb
>
> On Sat, Aug 6, 2016 at 12:28 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> I totally agree, that's why I'll never rely on Gradle in production
>>
>> Jacques
>>
>>
>> Le 06/08/2016 à 11:15, Taher Alkhateeb a écrit :
>>
>>> I also checked the second log, we have an issue with one of the
>>> dependencies on Shiro. Needs a little digging through but this is an issue
>>> you'd face regardless of the build system as it has to do with the remote
>>> repository.
>>>
>>> On Aug 6, 2016 10:11 AM, "Taher Alkhateeb" <[hidden email]>
>>> wrote:
>>>
>>> I would also like to add that massive production systems are deployed on
>>>> Gradle already. Our issues are familiarity, not stability.
>>>>
>>>> On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]>
>>>> wrote:
>>>>
>>>> Jacques, this has nothing to do with stability. Something is wrong in the
>>>>> configuration. The error message shows it clearly:
>>>>>
>>>>> * What went wrong: Task 'loadDefault' not found in root project 'build'.
>>>>>
>>>>> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <[hidden email]
>>>>> wrote:
>>>>>
>>>>> HI,
>>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>>>>>> /shell/logs/stdio
>>>>>>
>>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>>>>>> /shell/logs/stdio
>>>>>>
>>>>>> All is OK locally (here at least), so I guess better to wait and see.
>>>>>> Could though be that the error is everywhere, I don't want to swipe my
>>>>>> Gradle cache to verify!
>>>>>>
>>>>>> This shows that you should not rely on Gradle in production. I more and
>>>>>> more believe Pierre is right on this aspect!
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>>

[taher]

Oh, sorry if I wasn't clear, I meant java -jar does not improve the
situation because your issue is remote repository.

So my suggestion instead of copying jars locally (I don't see a lot of
difference because you have to fetch either way) is to keep them remote but
fine-tune the requirements. Right now, OFBiz is pulling waaaay to much! In
a sense OFBiz suffers from library bloat, and this is an area ripe for
improvement I think.

Taher Alkhateeb

On Sat, Aug 6, 2016 at 12:41 PM, Jacques Le Roux <
[hidden email]> wrote:

> Yes that's a better to way to say it, thanks.
>
> Indeed having collected and checked (I think at OWASP dependency checker)
> the libs and then stored them in a specific place seems a good way to go.
>
> I don't see much differences with java -jar. Where is it easier?
>
> Jacques
>
>
>
> Le 06/08/2016 à 11:30, Taher Alkhateeb a écrit :
>
>> Hi Jacques,
>>
>> I guess then you mean you never rely on a remote repository for
>> production,
>> Gradle is responsible for fetching, it is the repository that matters.
>> This
>> is an area where fine-tuning of the selected libraries is important rather
>> than dropping down to java -jar.
>>
>> Taher Alkhateeb
>>
>> On Sat, Aug 6, 2016 at 12:28 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>> I totally agree, that's why I'll never rely on Gradle in production
>>>
>>> Jacques
>>>
>>>
>>> Le 06/08/2016 à 11:15, Taher Alkhateeb a écrit :
>>>
>>> I also checked the second log, we have an issue with one of the
>>>> dependencies on Shiro. Needs a little digging through but this is an
>>>> issue
>>>> you'd face regardless of the build system as it has to do with the
>>>> remote
>>>> repository.
>>>>
>>>> On Aug 6, 2016 10:11 AM, "Taher Alkhateeb" <[hidden email]>
>>>> wrote:
>>>>
>>>> I would also like to add that massive production systems are deployed on
>>>>
>>>>> Gradle already. Our issues are familiarity, not stability.
>>>>>
>>>>> On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]
>>>>> >
>>>>> wrote:
>>>>>
>>>>> Jacques, this has nothing to do with stability. Something is wrong in
>>>>> the
>>>>>
>>>>>> configuration. The error message shows it clearly:
>>>>>>
>>>>>> * What went wrong: Task 'loadDefault' not found in root project
>>>>>> 'build'.
>>>>>>
>>>>>> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <
>>>>>> [hidden email]
>>>>>> wrote:
>>>>>>
>>>>>> HI,
>>>>>>
>>>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>>>>>>> /shell/logs/stdio
>>>>>>>
>>>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>>>>>>> /shell/logs/stdio
>>>>>>>
>>>>>>> All is OK locally (here at least), so I guess better to wait and see.
>>>>>>> Could though be that the error is everywhere, I don't want to swipe
>>>>>>> my
>>>>>>> Gradle cache to verify!
>>>>>>>
>>>>>>> This shows that you should not rely on Gradle in production. I more
>>>>>>> and
>>>>>>> more believe Pierre is right on this aspect!
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>

[Jacques Le Roux]

Le 06/08/2016 à 11:47, Taher Alkhateeb a écrit :
> Oh, sorry if I wasn't clear, I meant java -jar does not improve the
> situation because your issue is remote repository.

Our issue :), I agree we need to download the Internet anyway (kidding ;)) .
Note though that if nothing need to be updated (like locally) the cache is OK, so the copyLib task would be also. The problem here is more because
with ASF Buildbot we start anew each time.
It's not bad that ASF Buildbot does that, it warns us about possible issues when using Gradle in such a situation.

Also, as Pierre outlined, there are situations were you can't use Gradle but on dev machines. I experienced that, no servers were allowed to connect
to the Internet at all...

> So my suggestion instead of copying jars locally (I don't see a lot of
> difference because you have to fetch either way) is to keep them remote but
> fine-tune the requirements. Right now, OFBiz is pulling waaaay to much! In
> a sense OFBiz suffers from library bloat, and this is an area ripe for
> improvement I think.

Yes I know, we have still work on the plate...

Jacques

>
> Taher Alkhateeb
>
> On Sat, Aug 6, 2016 at 12:41 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Yes that's a better to way to say it, thanks.
>>
>> Indeed having collected and checked (I think at OWASP dependency checker)
>> the libs and then stored them in a specific place seems a good way to go.
>>
>> I don't see much differences with java -jar. Where is it easier?
>>
>> Jacques
>>
>>
>>
>> Le 06/08/2016 à 11:30, Taher Alkhateeb a écrit :
>>
>>> Hi Jacques,
>>>
>>> I guess then you mean you never rely on a remote repository for
>>> production,
>>> Gradle is responsible for fetching, it is the repository that matters.
>>> This
>>> is an area where fine-tuning of the selected libraries is important rather
>>> than dropping down to java -jar.
>>>
>>> Taher Alkhateeb
>>>
>>> On Sat, Aug 6, 2016 at 12:28 PM, Jacques Le Roux <
>>> [hidden email]> wrote:
>>>
>>> I totally agree, that's why I'll never rely on Gradle in production
>>>> Jacques
>>>>
>>>>
>>>> Le 06/08/2016 à 11:15, Taher Alkhateeb a écrit :
>>>>
>>>> I also checked the second log, we have an issue with one of the
>>>>> dependencies on Shiro. Needs a little digging through but this is an
>>>>> issue
>>>>> you'd face regardless of the build system as it has to do with the
>>>>> remote
>>>>> repository.
>>>>>
>>>>> On Aug 6, 2016 10:11 AM, "Taher Alkhateeb" <[hidden email]>
>>>>> wrote:
>>>>>
>>>>> I would also like to add that massive production systems are deployed on
>>>>>
>>>>>> Gradle already. Our issues are familiarity, not stability.
>>>>>>
>>>>>> On Aug 6, 2016 10:10 AM, "Taher Alkhateeb" <[hidden email]
>>>>>> wrote:
>>>>>>
>>>>>> Jacques, this has nothing to do with stability. Something is wrong in
>>>>>> the
>>>>>>
>>>>>>> configuration. The error message shows it clearly:
>>>>>>>
>>>>>>> * What went wrong: Task 'loadDefault' not found in root project
>>>>>>> 'build'.
>>>>>>>
>>>>>>> On Aug 6, 2016 9:49 AM, "Jacques Le Roux" <
>>>>>>> [hidden email]
>>>>>>> wrote:
>>>>>>>
>>>>>>> HI,
>>>>>>>
>>>>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1199/steps
>>>>>>>> /shell/logs/stdio
>>>>>>>>
>>>>>>>> https://ci.apache.org/builders/ofbiz-trunk/builds/1201/steps
>>>>>>>> /shell/logs/stdio
>>>>>>>>
>>>>>>>> All is OK locally (here at least), so I guess better to wait and see.
>>>>>>>> Could though be that the error is everywhere, I don't want to swipe
>>>>>>>> my
>>>>>>>> Gradle cache to verify!
>>>>>>>>
>>>>>>>> This shows that you should not rely on Gradle in production. I more
>>>>>>>> and
>>>>>>>> more believe Pierre is right on this aspect!
>>>>>>>>
>>>>>>>> Jacques
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>