Hello, Point 1/ is correct Point 2/ is not. The approach is now to remove inheritance and favor explicit dependency. a) But is it correct to declare dependencies of modules with scope runtime ? b) It was not the case previously, they has compile scope.
Thanks On Sat, Nov 9, 2019 at 11:35 AM Philippe Mouawad <pmoua...@apache.org> wrote: > Hello, > We have an issue with generated poms: > > 1/ Unspecified version in ApacheJMeter_core for jorphan: > > https://repo1.maven.org/maven2/org/apache/jmeter/ApacheJMeter_core/5.2/ApacheJMeter_core-5.2.pom > > We have this: > > <dependency><groupId>org.apache.jmeter</groupId><artifactId>jorphan</artifactId><version>unspecified</version></dependency> > > > 2/ The other poms are wrong. > Previously all modules inherited from ApacheJMeter_parent . > ApacheJMeter_parent pom has not been released and other modules do not > reference it anymore anyway nor do they mention mandatory dependencies. > > So this is a big problem for maven dependent projects > Can it be fixed without releasing a 5.2.1 ? > > I created https://bz.apache.org/bugzilla/show_bug.cgi?id=63910 > Regards > Philippe >
