arve
06/25/2025, 1:53 PMpackagePrefix
pattern (similar to gradle idea plugin: https://github.com/JetBrains/gradle-idea-ext-plugin/wiki#package-prefix )
2. Similarly, to define module name pattern. Example below
- We have multiple modules, and each module is split into contract
(interfaces) and service
(implementations), e.g.
manager/sales/contract # package manager.sales.contract
manager/sales/service
engine/pricing/contract
engine pricing/service # package engine.pricing.service
resource/orders/contract
resource/orders/service
Currently with Amper i get collisions in my experiment project (multiple projects named contract
) and had to modify the folder structure in order to build the project as a whole.
I guess these both are more candidates for plugins / extensions since potentially this is more programmatic than plain yaml if you want to let the user define this project-wide. Another approach could be having the user define things like packagePrefix, module name, artifact name in each project explicitly