Details
-
Wish
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.6.0
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
MNG-6530 Regression in ProjectBuilder when file change between invocations (introduced by MNG-6311)
- Closed
-
MNG-5669 same pom.xml is read multiple times
- Closed
-
MNG-6311 Maven intolerably slow when import scope used heavily in large project
- Closed
-
MNG-7027 Invalidate project cache upon changes
- Open