Re: Maven Build Cache Extension Hash Of Configuration

"Steffens, Tammo - ENCOWAY" <[email protected]>
Newsgroups gmane.comp.jakarta.turbine.maven.user
Message-ID <PAWP194MB231802CE9214836FFB5B6C2AF328A@PAWP194MB2318.EURP194.PROD.OUTLOOK.COM>
Hi Nils,
I did try, but after I looked at the source code, it appears because the default location of the configuration is placed inside an hidden directory, I can't add it as an input.

For reference (Tag 1.2.0) org/apache/maven/buildcache/checksum/MavenProjectInput.java:480

So this seems to be not supported at all.
________________________________
From: Nils Breunese <[email protected]>
Sent: Friday, August 8, 2025 5:22 PM
To: Maven Users List <[email protected]>
Subject: Re: Maven Build Cache Extension Hash Of Configuration

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Steffens, Tammo - ENCOWAY <[email protected]> wrote:

> Hi, I am currently trying to use the maven build cache extension. I wanted to ask if there is any way to include the extension config itself as part of the hash for every module. Because when I change the configuration, I want to invalidate old artifacts from the cache. Is there any known way to do it?

Have you tried via maven.build.cache.input?

https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fextensions%2Fmaven-build-cache-extension%2Fparameters.html%23project-level-properties&data=05%7C02%7CTammo.Steffens%40encoway.de%7Cef17a93983b44a75de2208ddd68f7bf1%7C37cf0ce8ac094e7d9ff2f1da44914b3e%7C0%7C0%7C638902633938582776%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3wGseYDV7aBTwVPHmygS4MRnGImgAlKEAsmZ5rWm42k%3D&reserved=0<https://maven.apache.org/extensions/maven-build-cache-extension/parameters.html#project-level-properties>

Nils.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.