clayburn commented on PR #39708: URL: https://github.com/apache/arrow/pull/39708#issuecomment-2012673472
> > For caching, there is no action needed. The one stipulation that should be noted is that the local cache is machine local > > @clayburn If you could help me with doubts regarding local development, I would appreciate it: > > 1. I am running `$ mvn clean install` and seeing that `/.m2/.gradle-enterprise` is populating with information. If I run `$ mvn clean install` again and haven't made any changes to my Java module projects, should it use the last cache? > 2. Is there a list of tasks that will be fetched from the cache before building it again (e.g. compile,...)? > > I would like to identify/map what the new advantages will be for developers on their loca machines. > > Thank you in advance for your support. @davisusanibar - So sorry for losing track of this: 1. Yes, such a build will use the cache. It also isn't necessarily even the "last" cache (i.e. the last build). It could be the case that you use cache entries from older builds as well. This can help, for example, when switching back and forth between feature branches. 2. We document the default cacheable goals [here](https://docs.gradle.com/enterprise/maven-extension/#cacheable_plugins_and_goals). It is possible to add goals if needed. We can explore this in the future to see if any in your project make sense to add. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
