But my point is the flatten plugin confuses tools and is awkward for many. Using MRP as I described would not confuse any tool as it would reqrite a pom as happens today. I'm also confused now as you are using MRP which the referenced comment is about.
On Tuesday, 14 December 2021 at 18:57:28 UTC Jesse Glick wrote: > On Tue, Dec 14, 2021 at 9:53 AM '[email protected]' via Jenkins > Developers <[email protected]> wrote: > >> there is possibility of something part way between the current CD flow >> (no junk pushes) and m-r-p >> > > As mentioned previously > <https://github.com/jenkins-infra/jenkins-maven-cd-action/pull/14#issuecomment-986806625> > > it is possible to just `mvn deploy` whatever stuff you like, including say > timestamps, and optionally pushing a tag, without pushing MRP-style > commits. Fine for things like services, but this will generally confuse any > tools which expect to *consume* your project as a dependency, since the > version coming from a local checkout of that tag will not match whatever > you deployed. That is why for purposes of Jenkins components including > plugins I do not recommend attempting to do anything between full JEP-229, > with a deterministic version scheme, and full MRP with the pair of junk > commits. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/205836d4-21ae-4d17-a6ac-c8e918603fcen%40googlegroups.com.
