Hi all Issue MDEP-791 looks more complicated and I don't see a consensus on how to resolve this. As a workaround we have a new option: ignoredNonTestScopedDependencies which allows us to exclude some or all artifacts from non-test-scoped.
We have resolved many other issues .... so I will release the next version in the next few days - of course if there will be no new objections. śr., 16 lut 2022 o 16:07 Slawomir Jaranowski <[email protected]> napisał(a): > Hi, > > I updated issue [1] with test project and describe steps what I did ... > Can anyone else try the same .... maybe I don't see something > > [1] https://issues.apache.org/jira/browse/MDEP-791 > > wt., 15 lut 2022 o 21:37 Elliotte Rusty Harold <[email protected]> > napisał(a): > >> On Tue, Feb 15, 2022 at 5:53 PM Slawomir Jaranowski >> <[email protected]> wrote: >> >> > Simply the problem is that dependencies present as transitive for any >> > dependency in compile scope should be not reported as "Non-test scoped". >> > So we should check if dependency listed as "Non-test scoped" are not >> > present as transitive dependency for other used in compile scope. >> > >> >> Can you elaborate on that? It seems to me that a normal unflattened >> pom.xml should not declare transitive dependencies. In fact it's >> pretty important that it not do so. For instance, if A's src/test >> depend on Guava but A's src/java does not depend on Guava, then A >> should only declare a test scope dependency on Guava, even if it also >> depends on something else at compile time that does depend on Guava. >> >> -- >> Elliotte Rusty Harold >> [email protected] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- > Sławomir Jaranowski > -- Sławomir Jaranowski
