Yep but it is not consistent since it is the same with but
there is no warning. So means that if you use system path or a custom
repository you have to use redefine it anyway in your project.
So if you think the warning should stay, it should be there for all
projects depending on anything else t
I don’t know what your warning reads, but mine says „will be unresolvable by
dependent projects“
--
http://bernd.eckenfels.net
Von: Romain Manni-Bucau
Gesendet: Saturday, September 25, 2021 7:50:07 PM
An: Maven Developers List
Betreff: Re: system path dependenc
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 E
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 wa
Le sam. 25 sept. 2021 à 09:04, Michael Osipov a
écrit :
> 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
>
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 de
