You have a point for downside projects - which is *not* what the warning
says (once again the message is technically wrong ;)).

So what is the solution?

Fix the message + document inline repo usage which is fully out of the
warning but has the same pitfall?

Le sam. 25 sept. 2021 à 17:42, Bernd Eckenfels <e...@zusammenkunft.net> a
écrit :

> Hello,
>
> I am a Repo user and despise binaries in git, therefore I would not run
> into this problem. It also means you might be outside of the maven
> conventions.
>
>  However I can see that you might need in expectional cases to access
> dependencies inside the project directory for building. But the warning is
> exactly that: if some other project depends on yours, they won’t be able to
> resolve. Maybe it is better to turn the local dependency into a new type
> compile-file, then it is not needed by your dependent projects (and  it
> should not produce a warning). Alternatively, maybe make it a plug-in
> dependency?
>
> So all in all, the warning is a good thing unless we have a way to not
> export that dependency into the consumer transitive tree (as those don’t
> know anything about your base)
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ________________________________
> Von: Michael Osipov <micha...@apache.org>
> Gesendet: Saturday, September 25, 2021 9:04:22 AM
> An: dev@maven.apache.org <dev@maven.apache.org>
> Betreff: Re: system path dependency warning, accurate or not?
>
> Am 2021-09-24 um 23:43 schrieb Benjamin Marwell:
> > Hi Michael!
> >
> > Setups like "${project.basedir}/m2/" are a common thing.
> >
> > While "system" scope was probably invented to use system
> > (i.e. jdk-related) jar files, but otoh
> > it is the only way to pull in artifacts
>
> Why aren't they installed locally or deployed to a hosted repo?
> This breaks our convention over configuration.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to