[MNG-6616] Create public API for Projects Artifacts Cache where one project can be invalidated

[jira-importer]

Balazs Zsoldos opened MNG-6616 and commented

By introducing the Projects Artifact Cache, single builds became faster. However, there are tools that embed Maven and do not restart the complete JVM process between builds: M2E, mvnsh, etc.

These tools cannot force the refresh of project artifacts currently based on a stable public API of Maven. It would be nice if there was a public stable API, where projects could be invalidated in the cache even one-by-one, so the recompilation of a project would be the fastest possible.

In case of designing such an API, it should not be only about project artifacts cache, so if new caches introduced later by maven internally, the API should invalidate the project-specific records in all of them.

I mean that the API interface should not be called ProjectArtifactCache, but more like ProjectCache, where the first current implementation would invalidate records in ProjectArtifactCache, but later if new caches are introduced, the same API call would manage those caches, too.

 

---

Affects: 3.6.0

Issue Links:

• MNG-6530 Regression in ProjectBuilder when file change between invocations (introduced by MNG-6311)

• MNG-5669 same pom.xml is read multiple times

• MNG-6311 Maven intolerably slow when import scope used heavily in large project

• MNG-7027 Invalidate project cache upon changes

0 votes, 5 watchers

[jira-importer]

Sylwester Lachiewicz commented

Linked to MNG-6311 and MNG-6530 (check also comments there)

[jira-importer]

Robert Scholte commented

Balazs Zsoldos I want to solve MNG-5669 and your issue seems to be related. This might be a right moment to work on this.

[jira-importer]

Guillaume Nodet commented

I believe https://github.com/apache/maven/pull/402 which is the first PR toward fixing MNG-6616 and MNG-7027 does indeed fix the problems mentioned in MNG-5669, MNG-6311 and MNG-6530. And it seems, also MNG-7063.

The Cache API proposed by the very issue would be based on https://github.com/mvndaemon/mvnd/tree/master/daemon/src/main/java/org/mvndaemon/mvnd/cache/factory . The work has mostly been done inside mvnd, but I'd like to backport as much as possible inside maven.

[jira-importer]

Mickael Istria commented

Do I get it right that with the change in #402 , then the cache is basically disabled by default except when using MavenCLI ? That would actually be perfect for cases embedding Maven API to use it for a long session.