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

ASF GitHub Bot commented on MBUILDCACHE-48:
-------------------------------------------

olamy commented on PR #51:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/51#issuecomment-1500832518

   worth to document the behaviour 
https://maven.apache.org/extensions/maven-build-cache-extension/parameters.html
   e.g this parameter can apply to single module(s) as well.




> Add ability to disable caching on a per-module level
> ----------------------------------------------------
>
>                 Key: MBUILDCACHE-48
>                 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-48
>             Project: Maven Build Cache Extension
>          Issue Type: New Feature
>          Components: remote build cache
>    Affects Versions: 1.0.0
>            Reporter: Alexander Eltsov
>            Priority: Major
>              Labels: pull-request-available
>
> Add ability to do the caching on a per-module level.
> This may be required in a case when a module is a final leaf of a reactor 
> tree, and its artefacts are not required by other modules as cached 
> dependencies. Hence eliminating some modules from caching will speed up build 
> and also lower the footprint size of a cached build.
>  
> E.g. in my project (where we have huge deployment artifacts in some of 
> modules) we reduced the cache footprint from 1.5G to 100M by introducing such 
> a capability



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to