Hello Michal, hello Robert, Thanks for the answers.
I am trying to reproduce this with a smaller project, but it is quite hard. The problem occurs with an inhouse project where we use inhouse plugins etc. We manage the lifecycle of standard packagings as well in the the extension. I wrote a FOSS derivate (not widely use) and will try to give a small example. Robert, did you mean to bisect the maven-core? Best Regards Mirko Robert wrote: > Hard to say: can you do a git bi-sect to discover the commit that changed the > behavior. Then we can see discuss if this change is intended or not. > Am 21.02.2021 um 10:31 schrieb Michael Osipov <micha...@apache.org>: > > Am 2021-02-19 um 18:52 schrieb Mirko Friedenhagen: >> Hello, >> * I now gave Apache Maven 4.0.0-alpha-1-SNAPSHOT >> (84a1ff2d5cb7bf49fa3171dd92f7ac088e837185) a try. >> * In my POM I configured the net.rumati.maven.plugins:velocity-maven-plugin >> which should render a HTML file. >> * The parent of the project has a global extension in the build section. >> * The jar of the extension does include a velocity which is picked up quite >> fine by the velocity-maven-plugin from >> the classpath by 3.6.3 but when using 4.0.0 I now need to add the extension >> jar as a dependency to the plugin. >> Is this an intended behavior? > > Can you reduce to a sample project? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
