[
https://issues.apache.org/jira/browse/MBUILDCACHE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946488#comment-17946488
]
Gili commented on MBUILDCACHE-116:
----------------------------------
Hi Sebastian,
Thank you for your reply.
I am happy to hear that this is just a configuration problem on my end.
Is there any chance of improving the documentation to warn about this
situation, and/or having maven-build-cache-extension log a warning if it finds
unexpected files/directories in the target directory that are not being cached?
It might prevent future users a lot of grief. Thank you.
PS: it's a bit weird to have a single configuration for a multi-project setup,
especially with regard to {{{}attachedOutputs{}}}. Is there a way to specify a
root configuration file and override it in a per-project basis?
> Extension fails to regenerate all files in target directory
> -----------------------------------------------------------
>
> Key: MBUILDCACHE-116
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-116
> Project: Maven Build Cache Extension
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Gili
> Priority: Major
>
> 1. Create a project with dependencies that contains:
> {code:java}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy-dependencies</id>
> <phase>prepare-package</phase>
> <goals>
> <goal>copy-dependencies</goal>
> </goals>
> <configuration>
>
> <outputDirectory>${project.build.directory}/lib</outputDirectory>
> <overWriteReleases>false</overWriteReleases>
> <overWriteSnapshots>false</overWriteSnapshots>
> <overWriteIfNewer>true</overWriteIfNewer>
> <useBaseVersion>false</useBaseVersion>
> <includeScope>runtime</includeScope>
> </configuration>
> </execution>
> </executions>
> </plugin>{code}
> 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?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
