Pretty sure it's the addition of javadocs that has changed the time recently.
-Dan On Fri, Jan 22, 2016 at 10:38 AM, Barry Oglesby <[email protected]> wrote: > I've used --profile before. It creates a nice report > in build/reports/profile like: > > :pivotalgf-assembly 33.731s (total) > :pivotalgf-assembly:srcDistTar 14.330s > :pivotalgf-assembly:distTar 7.054s > :pivotalgf-assembly:distZip 6.909s > :pivotalgf-assembly:srcDistZip 4.654s > :pivotalgf-assembly:compileTestJava 0.490s > > There is also a TaskExecutionListener that you can implement and configure, > although I haven't tried that. > > Barry Oglesby > GemFire Advanced Customer Engineering (ACE) > For immediate support please contact Pivotal Support at > http://support.pivotal.io/ > > > On Fri, Jan 22, 2016 at 10:24 AM, Kirk Lund <[email protected]> wrote: > > > The build has become painful. Is there an argument for gradle to show how > > much time each task takes? > > > > $ ./gradlew -Dskip.tests=true clean build > > <snip> > > :pivotalgf-assembly:processTestResources UP-TO-DATE > > :pivotalgf-assembly:testClasses > > :pivotalgf-assembly:checkMissedTests SKIPPED > > :pivotalgf-assembly:test SKIPPED > > :pivotalgf-assembly:check > > :pivotalgf-assembly:build > > :combineReports > > All test reports at C:\dev\gemfire_CLEAN\closed\build/reports/combined > > > > BUILD SUCCESSFUL > > > > Total time: 33 mins 9.708 secs > > $ > > >
