Hi Taher, Excellent work on gradle! I like your pluginLibsCompile very much.
Inspired by the pluginLibsCompile, is it possible to define a new clean plugin in build.gradle of a component to clean a log or index folder? Kind Regards, Shi Jinghai -----邮件原件----- 发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com] 发送时间: 2018年1月31日 0:54 收件人: OFBIZ Development Mailing List 主题: Re: [Proposal] Reducing the clean* operations in gradle Hi Jacques, Sure okay, we can keep cleanLogs and cleanFooterFiles. Any other opinions folks? Does anyone care for the other clean tasks to be isolated? On Tue, Jan 30, 2018 at 4:27 PM, Jacques Le Roux <jacques.le.r...@les7arts.com> wrote: > Hi Taher, > > I'd like to keep at least cleanLogs apart. > > It's sometimes useful to clean logs w/o changing anything else. > > Maybe cleanFooterFiles could be considered also but no strong opinion > > Jacques > > > > Le 29/01/2018 à 13:27, Nicolas Malin a écrit : >> >> Hello Taher, >> >> I haven't a strong opinion so your proposal seems to be good for slim >> the code. >> >> A noob question, can we move deleted tasks to the tools folder like >> ant previously ? >> >> Nicolas >> >> >> On 29/01/2018 11:31, Taher Alkhateeb wrote: >>> >>> Hello Everyone, I'm not sure why we have so many fine-grained clean >>> tasks, but to reduce clutter, I suggest to have only the following >>> clean operations in build.gradle: >>> >>> - cleanCatalina: To reset web server state to test stuff >>> - cleanData: To reset database state to test stuff >>> - cleanAll: To remove everything including above. >>> >>> So I suggest deleting all other clean* operations and incorporating >>> them into cleanAll. This would result in less clutter when issuing >>> "./gradlew tasks". >>> >>> Ideas? >>> >> >> >
