Timeline for spring-boot maven plugin re runs compile & test phase
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2014 at 13:11 | comment | added | Dave Syer | It's the same story for that - you have to tie a Maven goal to a specific lifecycle phase. Normally you don't run spring-boot:repackage as a standalone goal, you tie it to the "package" lifecycle in your pom (the starter-parent does that for you), and then it doesn't need to re-execute the earlier goals. | |
| May 22, 2014 at 12:47 | comment | added | spstorey | A better example is the repackage goal, by default it is attached to the maven verify stage (which itself ensures the previous phases compile, package etc have been completed). So if you run 'mvn clean install' you get phases clean > compile > test > package > verify > then spring-boot:repackage kicks off > compile > test > install... | |
| May 22, 2014 at 11:43 | history | answered | Dave Syer | CC BY-SA 3.0 |