Maven package aggregation project

problem description

my project is an aggregation project built with springboot and maven, and has a private maven library:
Project: shop
Module 1:email
Module 2:wechat
Module 3:service
Module 4:base

in which the base module depends on module 1, module 2, module 3

the environmental background of the problems and what methods you have tried

1. When I package the aggregation project shop (the package is successful), each module forms a jar package (and the jar package dependency of module 123 in the jar of module 4). The process should be to first hit module 1, module 2, module 3, and finally hit the package of module 4. When you hit the package of module 4, maven will go to the local library and compare it with the remote library to see if there are any dependencies of module 1, module 2, and module 3. If not, download it to the local library, and update it if it is old. Why doesn"t my native library have jar packages for modules 1, 2, and 3?

2. When I packaged module 4 separately, the local warehouse downloaded the packages of module 1, module 2, and module 3.

Why doesn"t the local warehouse download it in case 1?
do I misunderstand the packaging process?

Apr.09,2021
Menu