You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Alexander Eltsov (Jira)" <ji...@apache.org> on 2023/03/21 11:15: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 ]

Alexander Eltsov updated MBUILDCACHE-48:
----------------------------------------
    Description: 
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

  was:Add ability to disable generated source restoration on a per-module level. This is required to overcome issues with some weird Maven plugins which go nuts when cached generated sources are present and produce incorrect build result


> 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
>
> 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)