Hi Olivier,
Okay, so I guess you'd like to run gradle inside eclipse. This sort of
reminds me of the days when I ran OFBiz directly inside eclipse which had
multiple disadvantages (relying on eclipse environment, might rely on a
different JVM and other entanglements to eclipse). So in general I
Hi Taher,
Having OFBiz project declare as a gradle project in eclipse is useful to
see all gradle task and be able to run it.
With these modifications it's the case.
It's not an important point and gradle --gui (even if it less clear) is
usable.
Olivier
Le 25/11/2016 à 19:58, Taher Alkhateeb
End of my test ;-) and my conclusions :
To have ofbiz in eclipse and being declare as a gradle project, it's
necessary to complete the gradle eclipse task before doing the import
existing project in eclipse :
1°) to have a correct .project file
it's necessary to add to build.gradle (before
It seems that the only problem is in the .project file because after a
cleanAll if I use ./gradlew eclipse and after I replace the .project
file by
ofbiz
org.eclipse.jdt.core.javabuilder
Thank you very much Taher,
I will used the gui.
The fun fact is : when I test it (and compare what I have in eclipse), I
have used the cleanEclipseClasspath and after the eclipseClasspath and .
it seen to solve the eclipse pb !
So I will continue to trying to solve the way to have ofbiz with
Hi Olivier,
It might be a bit quirky to control it from eclipse because of the way it
treats sub-projects. If you like a GUI to work with, then I recommend
./gradlew --gui. It's fun to work with and you can save your favorite
commands.
Cheers,
Taher Alkhateeb
On Wed, Nov 23, 2016 at 7:41 PM,
I'm trying to load ofbiz project in eclipse and declare it as a gradle
but it generate a lot of sub-project and error in java build.
My process :
1) download ofbiz
2) ./gradlew eclipse
3) open eclipse (Neon Java default config) in a new workspace,
4) import existing project
ofbiz is recognize as
