Hervé Boutemy opened MARTIFACT-78 and commented
root/aggregate module notion is key to clarify the (aggregated) project vs the individual modules
let's display it to increase visibility
context: Maven perfectly defines gav coordinates for each module
but for complex project, which are multi-module, what is the project's coordinate? Should it be one of the modules gav? which one?
this is one of the complexities of Reproducible Central: choice of directory where to store project's rebuilds info
for simple mono module, it is dead simple: the ga is there to store versions
for multi-module, it's less obvious: ga of root module? (even if it contains "-root" or "-parent" ugly suffix) what if there are multiple groupIds? what if root module is not parent? what if root module ga changes over time/versions?
Affects: 3.5.3
Issue Links:
Remote Links:
Hervé Boutemy opened MARTIFACT-78 and commented
root/aggregate module notion is key to clarify the (aggregated) project vs the individual modules
let's display it to increase visibility
context: Maven perfectly defines gav coordinates for each module
but for complex project, which are multi-module, what is the project's coordinate? Should it be one of the modules gav? which one?
this is one of the complexities of Reproducible Central: choice of directory where to store project's rebuilds info
for simple mono module, it is dead simple: the ga is there to store versions
for multi-module, it's less obvious: ga of root module? (even if it contains "-root" or "-parent" ugly suffix) what if there are multiple groupIds? what if root module is not parent? what if root module ga changes over time/versions?
Affects: 3.5.3
Issue Links:
Remote Links: