Gili created MBUILDCACHE-116:
--------------------------------
Summary: 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
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)
