[
https://issues.apache.org/jira/browse/MBUILDCACHE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956926#comment-17956926
]
Olivier Lamy commented on MBUILDCACHE-101:
------------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-build-cache-extension#340|https://github.com/apache/maven-build-cache-extension/issues/340].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> mvn test fails on missing classes after mvn compile
> ---------------------------------------------------
>
> Key: MBUILDCACHE-101
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-101
> Project: Maven Build Cache Extension (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Amir Hadadi
> Priority: Major
> Labels: pull-request-available
>
> Using a project whose artifacts are not cached locally or remotely, do the
> following:
> {code:java}
> mvn compile{code}
> This will compile the code and mark the compile plugin goal as cached.
> If you now run:
> {code:java}
> mvn clean test{code}
> You will see in the log:
> {code:java}
> Skipping plugin execution (cached): compiler:compile{code}
> and then the build will fail due to missing classes, since it will not run
> the compile phase again (as it was marked cached) and it has nowhere to pull
> the compiled classes from.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
