[MBUILDCACHE-116] Extension fails to regenerate all files in target directory

**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** opened **[MBUILDCACHE-116](https://issues.apache.org/jira/browse/MBUILDCACHE-116?redirect=false)** and commented

1. Create a project with dependencies that contains:

```java

    org.apache.maven.plugins
    maven-dependency-plugin
   
       
            copy-dependencies
            prepare-package
           
                copy-dependencies
           
           
                ${project.build.directory}/lib
                false
                false
                true
                false
                runtime
           
       
   

```

2. Run "mvn verify".
3. Notice that the "target" directory contains the main JAR file and "target/lib" contains the JAR file's dependencies
4. Delete the target directory
5. Run "mvn verify" again.
6. Notice that "target" directory contains the main JAR file but the "target/lib" directory is missing.

{**}Expected behavior{**}: "mvn verify" should always generate the same output.

This might be a regression of https://issues.apache.org/jira/browse/MBUILDCACHE-67. Per https://stackoverflow.com/q/78057064/14731 this issue existed back in version 1.0.1, was fixed by version 1.1.0, but it seems to be back now.

Can someone please take a look at this?

---

**Affects:** 1.2.0

Reproduce the issue with the Maven dependency-plugin configuration in the report: run `mvn verify`, delete `target`, and run it again. Compare the generated `target` and `target/lib` contents, then investigate the build-cache extension behavior related to MBUILDCACHE-67. Done means repeated clean builds consistently regenerate the dependency JARs in `target/lib`.

Written by the indexing model from the issue text.