jira-importer opened a new issue, #270:
URL: https://github.com/apache/maven-build-cache-extension/issues/270

   **[Hongxin 
Liang](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=honnix)** 
opened 
**[MBUILDCACHE-78](https://issues.apache.org/jira/browse/MBUILDCACHE-78?redirect=false)**
 and commented
   
   In a multimodule project, as a simplest example: 
[https://github.com/honnix/cache](https://github.com/honnix/cache) , "mvn 
compile" with build cache enabled doesn't play well with Maven reactor. A few 
scenarios I have tested in the provided repro example:
   1. With a clean environment (no build cache, no "mvn install" have been done)
      1. Run "mvn compile" and everything works
      2. Modify (putting a random empty line will suffice) class "B" in module 
"b"
      3. Run "mvn compile" again, and now it fails when trying to download 
snapshot of module "a" from maven central (after failing to find that in my 
local repo)
   2. With a clean environment (no build cache)
      1. Run "mvn install" and everything works
      2. Modify class "A" in module "a" to rename the method
      3. Run "mvn compile" for the first time, and it fails to compile due to 
renaming of the method in class "A"
      4. Run "mvn compile" for the second time, nothing fails but apparent the 
code is still wrong; run more "mvn compile" and still nothing fails
      5. Running "mvn install" fails the build due to compilation error
   
   I'm not entirely sure I am doing things properly and I'm not sure whether 
the config is correct either (I took the example as 
https://maven.apache.org/extensions/maven-build-cache-extension/maven-build-cache-config.xml
 with modification to disable remote cache).
   
   
   ---
   
   **Affects:** 1.1.0
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to