You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (Jira)" <ji...@apache.org> on 2023/04/17 03:11:00 UTC

[jira] [Updated] (MBUILDCACHE-48) Add ability to disable caching on a per-module level

     [ https://issues.apache.org/jira/browse/MBUILDCACHE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MBUILDCACHE-48:
------------------------------------
    Fix Version/s: 1.0.1

> 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
>             Fix For: 1.0.1
>
>
> 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)