I'm already used to it :D (a bit too much I'd say, but that's life, hè)
BTW this question was related with the work I did recently on the Eclipse+Tips
wiki page and especially
https://cwiki.apache.org/confluence/display/OFBIZ/Eclipse+Tips#EclipseTips-EclipseandGradle
I think we have now a good way to handle plugins as a sub-project in Eclipse
which is quite convenient
Comments are welcome...
Jacques
Le 16/01/2018 à 11:12, Michael Brohl a écrit :
Yes, you have to run "gradlew cleanAll eclipse ... " to regenerate the eclipse
file.
You'll get used to it after a while...
Am 16.01.18 um 10:46 schrieb Jacques Le Roux:
But then it's regenerated, right?
Because, if I'm not wrong, the only trouble I have in Eclipse, and need to run
the eclipse task again, is after I ran cleanAll, right?
Jacques
Le 16/01/2018 à 10:01, Taher Alkhateeb a écrit :
Every time you create a new package or change the structure of packages you
need to run the gradle eclipse task to repopulate the classpath. And to do
that you need to delete the eclipse files first
On Jan 16, 2018 11:09 AM, "Jacques Le Roux" <[email protected]>
wrote:
Hi Taher, All,
Could we not delete the .project and .classpath file when using cleanAll
or possibly run the eclipse task at the end of cleanAll?
For the 2nd option, I understand it makes no sense for non Eclipse users,
but maybe having the .project and .classpath file for them would not be an
issue, opinions?
Thanks
Jacques
