I dislike the idea to "toggle logic". This way, we would have 3 mojos with 3 different logic. Is simpler to understand, that invoke same mojo to do this or that, based on toggle.
T On Sat, Feb 25, 2023, 13:18 Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi, > > Maybe I missed some details but n unsafe toggle (parameter) to deploy > sounds like a good compromise to me. > Too much overlapping goals sounds weird and hard to understand. > > Le sam. 25 févr. 2023 à 12:39, Tamás Cservenák <ta...@cservenak.net> a > écrit : > > > Howdy, > > > > Here is this thread: > > https://lists.apache.org/thread/lbbd5n92xjksyf53mlf12togxrvdbvhl > > > > In short, user is _partially_ building a module, and invokes > deploy:deploy, > > that now fails, as since 3.x version of install/deploy, there is a > "safety > > check" in these mojos, to not deploy partially (here it would deploy POM > > with packaging jar, but the main artifact is NOT built, only a classified > > one). User opted for this solution as it is "one liner", as deploy-file > > would require MANY parameters (does not reuse POM values). > > > > === > > > > So, what about a new mojo for install/deploy plugins? (symmetrically for > > both install/deploy plugins, but explaining on case of deploy) > > > > deploy:deploy -- unchanged, works as today: "deploy project" and enforces > > repository hygiene, fails if POM refers to main artifact that is not > > present > > deploy:deploy-file -- unchanged, works as today, "deploy file" and > neglects > > exiting POM and requires MANY parameters > > > > and a new goal: > > deploy:deploy-artifacts -- this is a "mesh" between two above but would > > NEVER deploy POM. What this goal would essentially do, is "just blindly" > > deploy any (packaged) artifact (main or attached/classified) but would > NOT > > deploy a POM. Even if one classified artifact is present, it would deploy > > it. It MAY fail if invoked and the project has NOTHING to deploy. So, > like > > deploy-file but needs a project (to reuse coordinates from it) > > > > Related issues: > > https://issues.apache.org/jira/browse/MDEPLOY-205 > > https://issues.apache.org/jira/browse/MINSTALL-118 > > > > WDYT? > > Tamas > > >
