yes it's regenerated but you have to remove it to regenerate it otherwise you'll have a corrupted file (or you'd need to code it in a different way). I'm not sure I understand your question, but either way I prefer keeping things as is. Back in the old days managing those files was a real pain.
On Tue, Jan 16, 2018 at 12:46 PM, Jacques Le Roux <[email protected]> wrote: > 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 >>> >>> >
