Howdy, Basil's issue is made me realize: o.c.p:p-u 4.x that depends on -> o.c.p:p-xml 4 that depends on -> o.a.m:m-api-xml that depends on -> o.a.m:m-api-meta
This means that p-u pulls in new Maven4 API bits. Hence, Maven 3 plugin, that is built against maven-plugin-api 3.x, if switched to p-u 4, would start receiving bits of Maven4 new API... This is a big no for me, not to mention how this can prove problematic down the road too: this means that today (as all this is "just on CP") mvn3 plugin could use bits of Maven4 API that later -- if run in Maven4 -- becomes forbidden/unavailable... So, IMHO this just proves, that Maven 3.x level plugins should stick with p-u 3.x On Fri, Sep 8, 2023 at 6:24 PM Basil Crow <m...@basilcrow.com> wrote: > I raised this issue in > > https://github.com/jenkinsci/maven-hpi-plugin/pull/490#issuecomment-1557970717 > but did not receive a response. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
