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 <
[email protected]> 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" <[email protected]>
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" <[email protected]>
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" <[email protected]
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
