Classification: For internal use only Hi Enrico,
It's not open sourced for now. We need to spend much efforts according with DB policies/procedures to make it open source. That's why we started this discussion, we don't want to waste time if change conceptually wrong(from Maven Dev Community perspective) and will be rejected. To sum up discussion: no go for this change. In some time we will wrap caching module in extension. Regards, Max -----Original Message----- From: Enrico Olivelli [mailto:[email protected]] Sent: Saturday, September 21, 2019 9:50 AM To: Maven Developers List <[email protected]> Subject: Re: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching Hi Maximilian, is there anyway to see this work ? is it already open source? (I am sorry, maybe I missed some email with links) Enrico Il giorno ven 20 set 2019 alle ore 19:30 Alexander Ashitkin < [email protected]> ha scritto: > 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 <[email protected]> > wrote: > > On Thu, Sep 19, 2019 at 7:48 AM Alexander Ashitkin > > <[email protected]> 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: [email protected] For > > additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For > additional commands, e-mail: [email protected] > > --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.
