> Op 1 apr 2025 om 13:07 heeft Mantas Gridinas <mgridi...@gmail.com> het > volgende geschreven: > > If the other dependency is also managed by maven, you can build it with > install goal, and it will end up in your local repository and you won't > need to readd it every time. Looking at jar-with-dependencies assembly > definition it only includes runtime dependencies, and this imposes a > question - are system dependencies considered available at runtime? > https://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies > > >> On Tue, Apr 1, 2025, 13:52 w f <wm_...@yahoo.com.invalid> wrote: >> >> >> My dependencies configured like this: >> >> <dependency> >> <groupId>org.pynkon.tm.toolib</groupId> >> <artifactId>tm-toolib</artifactId> >> <version>1.0</version> >> <scope>system</scope> >> >> <systemPath>${project.basedir}/../tm-toolib/target/tm-toolib-1.0-SNAPSHOT.jar</systemPath> >> </dependency> >> <dependencies> >> (I get warnings about my tm-toolib but only warnings.)
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#System_Dependencies Putting your own projects is not what the (already deprecated) system scope is meant for. You should mvn install (or deploy) them if it's not a multimodule project. If you build as a multi-module project simply put the dependency in and all will work just fine, even with only mvn package (it will resolve the jar from target because it's part of the same multimodule built and will know to first build tm-toollib before the other two due to the internal dependencies)
