@Michael Osipov Benjamin sumarrize the point, you can
say 'system is for outside" but then how do you handle "inside"? You fake a
repo in project/m2 and add a repository? This is the whole point of this
questoin and I'm not sure we cover it in the doc properly. Plus the fact
the warning is technic
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
which are stored next to the project's directory.
If you don't think "system" scope should
elharo closed pull request #70:
URL: https://github.com/apache/maven-doxia/pull/70
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
Am 2021-09-24 um 16:42 schrieb Romain Manni-Bucau:
Hi all,
wonder if there is any reason to see this warning when using a jar in the
project in system scope:
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for io.yupiik.foo:foo:jar:0.0.1-SNAPSHOT
[WARNING]
Hi all,
wonder if there is any reason to see this warning when using a jar in the
project in system scope:
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for io.yupiik.foo:foo:jar:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.systemPath' for foo:bar:jar
