[
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604837#comment-17604837
]
ASF GitHub Bot commented on MBUILDCACHE-22:
-------------------------------------------
AlexanderAshitkin commented on code in PR #24:
URL:
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r970815746
##########
src/main/java/org/apache/maven/buildcache/BuildCacheMojosExecutionStrategy.java:
##########
@@ -96,6 +97,7 @@ public void execute( List<MojoExecution> mojoExecutions,
// execute clean bound goals before restoring to not
interfere/slowdown clean
CacheState cacheState = DISABLED;
CacheResult result = CacheResult.empty();
+ boolean skipCacheLookup = cacheConfig.isSkipLookup() ||
MavenProjectInput.shouldSkipCacheLookup( project );
Review Comment:
regarding the naming - lets call it `skipCache`. Gradle has similar
parameter to force rebuild named `--no-build-cache`.
> Add possibility to skip cache lookup
> ------------------------------------
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
> Issue Type: New Feature
> Components: remote build cache
> Affects Versions: 1.0.0-alpha
> Reporter: Alexander Eltsov
> Priority: Major
> Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project
> (required to get some modules always built e.g. via a profile - e.g. I have
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just
> current matching versions are not taken from caches
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
