Gradle clean basically cleans the build directory used in java compilation. In the task compileContentSass for instance you source from $contentDir and write to $generatedAssetDir and these are not part of the java eco system.
What you should do is create a new task which deletes all the directories you use and then do a clean.dependsOn(myCleanTask) so that is is run when clean is run. Another thing is noticed was you have a task to stop and start tomcat, there is a nice plugin on github (bmuschko/gradle-tomcat-plugin) which allows you to redeploy core easily. On 26 Feb 2018 10:42, "Neil C Smith" <[email protected]> wrote: > On Mon, 26 Feb 2018 at 07:54 Antonio <[email protected]> wrote: > > > This has now been merged to master, we think we comply with ASF's > > podling website requirements. > > > Woot! :-) > > Some other enhancements & to-dos as seen in the thread & elsewhere: > > ... > > - The README at > > > > https://github.com/apache/incubator-netbeans-website/ > tree/master/netbeans.apache.org > > explains how Wade's script work, how to run a preview site yourself, etc. > > > > > Note (for others) that you might need to run these commands to get the > correct output - > > ./gradlew clean > ./gradlew preprocessContent --rerun-tasks > ./gradlew bake > > One other useful task would be for someone who understands Gradle better > than Antonio or I to have a look at why the build (or sass plugin in > particular) is incorrectly caching even after cleaning. > > Best wishes, > > Neil > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org >
