Thanks Jacques for this solution.
I was a little afraid after reading that you moved 1.2 Go data and had
path length problem, that's why I thought this was a problem linked more
to the Windows Os.
I'll try this the next time I'll encounter this problem, it seems to be
a pretty clear solution.
On 30/08/2016 11:01, Jacques Le Roux wrote:
Hi Florian,
If you read my post (the 1st one in this thread) you will see that the
solution for your problem is to change the GRADLE_USER_HOME
There are 2 possiblities:
1. using the <<-g, --gradle-user-home Specifies the gradle user home
directory.>> Gradle option. It did not work for me initially because I
missed
the wrapper (ie copied only the caches). I just tested it works.
2. Setting the GRADLE_USER_HOME in the gradle script (gradlew.bat or
gradlew) in OFBiz root folder. I used: set GRADLE_USER_HOME=c:\gradle
You can then copy the Gradle stuff anywhere you want
HTH
Jacques
Le 30/08/2016 à 09:56, Montalbano Florian a écrit :
Hi Taher, All,
thanks a lot for this thorough explanation.
I just encountered the case where I had no internet connexion to
fetch the dependencies. After searching for a while, I succeeded in
resolving this problem by using what you said in your point "1- No
internet connection" . The only difference is that I needed to have
exactly the same absolute path to the .gradle folder between the two
computers. But maybe it was because I miss-used the '--offline' flag.
I think that as long we can do this, there shouldn't be too much
problem for specific deployment. I can understand the possibility
where the server can't be connected to the wild web (for security
stuff) but I lack the experience to know if there is case where
gradle may not be allowed (with a good motive).
Thanks again,
Have a nice day.
