You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/08/21 14:40:00 UTC

[jira] [Commented] (MBUILDCACHE-101) mvn test fails on missing classes after mvn compile

    [ https://issues.apache.org/jira/browse/MBUILDCACHE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875519#comment-17875519 ] 

ASF GitHub Bot commented on MBUILDCACHE-101:
--------------------------------------------

reda-alaoui opened a new pull request, #176:
URL: https://github.com/apache/maven-build-cache-extension/pull/176

   This PR makes sure any cached build that doesn't involve phase `package` is considered as invalid.
   
   ------
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [X] Make sure there is a [MBUILDCACHE JIRA issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed 
          for the change (usually before you start working on it).  Trivial changes like typos do not 
          require a JIRA issue.  Your pull request should address just this issue, without 
          pulling in other changes.
    - [X] Each commit in the pull request should have a meaningful subject line and body.
    - [X] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles`,
          where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue. Best practice
          is to use the JIRA issue title in the pull request title and in the first line of the 
          commit message.
    - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will 
          be performed on your pull request automatically.
    - [X] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> 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
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Amir Hadadi
>            Priority: Major
>
> 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)