[
https://issues.apache.org/jira/browse/MBUILDCACHE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788759#comment-17788759
]
ASF GitHub Bot commented on MBUILDCACHE-74:
-------------------------------------------
mweirauch commented on PR #110:
URL:
https://github.com/apache/maven-build-cache-extension/pull/110#issuecomment-1822705452
Oops, I didn't pay attention and force pushed a local change to the root
pom.xml which helps vscode to actually recognize the generated sources folder
for the mdo generated models. This now landed on master. I am very sorry for
this mistake!
Please let me know if you want to keep it. It shouldn't hurt the build, but
it's still IDE specific. (vscode uses Eclipse' m2e backend which needs some
help with the classpath extension; dunno specifically if this change also helps
Eclipse users as well)
> Old POM builds are not cleaned up from local cache
> --------------------------------------------------
>
> Key: MBUILDCACHE-74
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-74
> Project: Maven Build Cache Extension
> Issue Type: Bug
> Affects Versions: 1.0.1
> Reporter: Michael Weirauch
> Assignee: Olivier Lamy
> Priority: Minor
> Labels: pull-request-available
>
> We are operating a multi-module mono repository with an in-tree parent which
> is used by all modules. The parent is modified regularly. While debugging I
> realized that stale cache entries for the parent are still present in the
> local build cache directory allthough "maxBuildsCached" is set to "1".
> I have a fix ready, but I am still trying to figure if I can hook into an
> existing test or create a dedicated one. (I am not that familiar with the
> codebase.)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
