Replies: 1 comment 2 replies
-
|
It would be nice indeed, but then you should somehow offer the same flexibility the archiver plugin offers today I would say. What about its delivery then? Would the generated archive be attached to the project as additional artifact or not? I think it's quite a complex topic for, maybe, little added value since you may do it cleanly with Maven multi-modules. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
A common pattern that I have seen is the use of
ziparchives containing protobuf sourcesthat are then added as a dependency by other projects.
Currently, if a Maven project wishes to create one of these ZIPs, it is a somewhat manual
process that involves setting up the Maven Archiver plugin in a specific way.
I think we could make that easier for users by potentially having a goal in this project that
concerns itself with generating these kinds of archives automatically.
One idea could be to introduce a new project packaging type that limits the Maven phases that get run so that only the required steps get called, e.g:
This would then be able to register the ZIP as the project artifact for deployment to a Maven Central registry or similar.
Beta Was this translation helpful? Give feedback.
All reactions