Changing property in parent pom building all modules #597
Replies: 1 comment
-
This is to be expected, given how GIB works today. Having said that, this limitation has been bugging me for a while too. To give an idea how complex it can get: imagine a The only advice I can give right now is to either live with it (given that updates don't happen all the time, except for bigger projects) or to not declare things like that in the parent, as unfamiliar as that might feel. |
Beta Was this translation helpful? Give feedback.
-
I started playing with GIB again in our project after #579, is fixed. One query again
We have a multi-module project which is structured like below
Let's say a dependency,
zstd-jni
is needed in most of the modules (e.gmodule1
&module2
). Then what we do is specify the version as a property inparent/pom.xml
(so that the version remains consistent across the project).In
module1
andmodule2
,pom.xml
then we add the dependency like belowIn this case, GIB is identifying the changed artifact as
parent
which in turn is building up the whole project. Ideally, I would have wanted onlymodule1
andmodule2
to be built as these are the modules usingzstd-jni
, whose version is changed.Is this expected? If yes what is the recommended way of handling this case?
Beta Was this translation helpful? Give feedback.
All reactions