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

Maximilian Novikov edited comment on MBUILDCACHE-45 at 8/22/23 3:43 PM:
------------------------------------------------------------------------

spring-boot-maven-plugin tries to attach artifacts from 'target' folder instead 
of using the actual data from maven model where artifacts are pointed to cached 
data... i'd say it should be fixed in spring-boot-maven-plugin


was (Author: JIRAUSER299713):
spring-boot-maven-plugin tries to attach artefacts from 'target' folder instead 
of using the actual data from maven model where artefacts are pointed to cached 
data... i'd say it should be fixed in spring-boot-maven-plugin

> Compiled classes are not copied/restored to target, causing higher phase 
> builds to fail
> ---------------------------------------------------------------------------------------
>
>                 Key: MBUILDCACHE-45
>                 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-45
>             Project: Maven Build Cache Extension
>          Issue Type: Bug
>         Environment: windows
>            Reporter: Miguel Ortega
>            Priority: Major
>         Attachments: maven-cache.zip
>
>
> +*Step to reproduce*+
> 1. Execute a first command on a pristine projet( NO CACHE has ever been 
> stored)
> {code:java}
> mvn test{code}
> Results are cached (contrary to documentation that states that "cache will 
> kick-in automatically on every lifecycle build of phase {{package}} or 
> higher.") This could also be a feature since tests can be skipped if nothing 
> changes.
> 2 . But if I run next: 
> {code:java}
> mvn clean verify
> #OR
> mvn clean install{code}
> Then the build fails
> {code:java}
> [ERROR] Failed to execute goal 
> org.springframework.boot:spring-boot-maven-plugin:3.0.2:repackage (repackage) 
> on project demo: Execution repackage of goal 
> org.springframework.boot:spring-boot-maven-plugin:3.0.2:repackage failed: 
> Unable to find main class -> [Help 1]
> [ERROR]
>  {code}
> The root cause seems to be that after "clean", the maven target directory is 
> cleaned and even if the cache is detected, classes are not restored to the 
> target folder anymore
> {code:java}
> [INFO] Attempting to restore project com.example:demo from build cache
> [INFO] Remote cache is incomplete or missing, trying local build for 
> com.example:demo
> [INFO] Local build found by checksum 596f60b3f5056d7d
> [INFO] Found cached build, restoring com.example:demo from cache by checksum 
> 596f60b3f5056d7d
> [INFO] Project com.example:demo restored partially. Highest cached goal: 
> test, requested: install
> [INFO] Skipping plugin execution (cached): resources:resources
> [INFO] Skipping plugin execution (cached): compiler:compile
> [INFO] Skipping plugin execution (cached): resources:testResources
> [INFO] Skipping plugin execution (cached): compiler:testCompile
> [INFO] Skipping plugin execution (cached): surefire:test {code}
> *+Workaround+*
> Manually remove cache data or disable cache via command line argument
> *+Environment+*
> {code:java}
> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: <REDACTED>
> Java version: 17.0.1, vendor: Eclipse Adoptium, runtime: <REDACTED>
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to