[ 
https://issues.apache.org/jira/browse/MNG-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407201#comment-17407201
 ] 

Mickael Istria commented on MNG-6616:
-------------------------------------

Do I get it right that with the change in 
[https://github.com/apache/maven/pull/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.

> Create public API for Projects Artifacts Cache where one project can be 
> invalidated
> -----------------------------------------------------------------------------------
>
>                 Key: MNG-6616
>                 URL: https://issues.apache.org/jira/browse/MNG-6616
>             Project: Maven
>          Issue Type: Wish
>          Components: Bootstrap & Build
>    Affects Versions: 3.6.0
>            Reporter: Balazs Zsoldos
>            Priority: Major
>
> 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.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to