Hi Martijn 
thanks for positive feedback.

Regarding IDE part, yes you're right on integration part, but still there 
important cases when cache helps:
1) you need to navigate less in project as top level targets fast enough to not 
drill down
2) if you need to build a part of project (say only rest of wicket) you need to 
provide up-to-date rest dependencies which are not active in the subproject - 
and caches restores missing pieces for you without rebuilding remaining part of 
the project
3) If you need to test project and invoke test - cache saves your time (as 
gradle does) on unchanged pieces
4) and because tests run faster you can try run slow tests which often too 
expensive in rapid development

So maven integration in Intellij works nice. There is nothing super smart here, 
just sharing how i benefit from the cache in everyday ide work

Thank you!

On 2019/09/19 11:28:48, Martijn Dashorst <martijn.dasho...@gmail.com> wrote: 
> On Thu, Sep 19, 2019 at 7:48 AM Alexander Ashitkin
> <ashitkin.a...@gmail.com> wrote:
> > Configuration:
> > * verify -T4 -P default,all-shapshots-repos
> > * my project config (might be suboptimal for wicket)
> > * scala tests disabled in 2 modules (caused bytecode version conflict on my 
> > machine)
> >
> > Results
> > Clean state (cache disabled):                           15:58 min
> > Second run, target up to date (cache disabled):      10:20 min
> > Fully cached (no changes):                                      17.507 s
> > wicketstuff-jwicket-tooltip-wtooltips changed:          34.936 s
> > wicketstuff-rest-utils changed:                                 54.040 s
> >
> > If you want to try other modules - please let me know.
> 
> Nice results!
> 
> > regarding ide - it's a usual maven installation, so any ide with maven 
> > integration should benefit from cache them maven action invoked
> 
> My instinct says that an IDE as Eclipse won't benefit much from it, as
> it has its own build lifecycle. Only when you invoke a commandline
> Maven action (such as generate-sources) one might have a benefit.
> 
> So in the day-to-day life the caching might not be as beneficial for
> developers, but commandline builds happen often enough to make this
> matter.
> 
> Martijn
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to