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 modules are automatically available or you once install the dependent module, then it also resolves normally. (Also not specifying the version). Technically I think some plugins allow to change the scopes they consider, but like with everything else in Maven land, don’t stray from the path, you just hurt yourself down the line. Gruss Bernd w f wrote on 1. Apr 2025 12:50 (GMT +02:00): > <scope>system</scope> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
