Hello,
the reason why it is not picked up as a dependency is, because it is a system
scope, which means “provided” by the system. If you change that to default
scope, it will be considered.
You don’t need to specify the relative path, you either build the parent
reactor, then the neighbour mo
> Op 1 apr 2025 om 13:07 heeft Mantas Gridinas 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 assem
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
I'm working on an application suite which consists of three (3) Maven projects:
* tm-server
* tm-client
* tm-toolib
Current 3rd-party dependencies for tm-server and tm-client are an MQTT library
and a database library.
Both tm-server and tm-client are dependent on my tm-toolib. tm-toolib has no
