Why not centralize Phoebus module versions in parent pom ?

[flef]

Hi,

It seems that all the modules have similar life cycles (a new module version is released for each Phoebus version).
I'm wondering if there is a reason to have not centralized phoebus sub-modules version in parent pom ?

For instance, instead of having

<dependency>
      <groupId>org.phoebus</groupId>
      <artifactId>core-framework</artifactId>
      <version>5.0.3-SNAPSHOT</version>
</dependency>

We can put a variable ${phoebus.version} defined as follow in the parent pom :

<properties>
    <phoebus.version>5.0.3-SNAPSHOT</phoebus.version>
</properties>

And used as follow everywhere :

<dependency>
      <groupId>org.phoebus</groupId>
      <artifactId>core-framework</artifactId>
      <version>${phoebus.version}</version>
</dependency>

Are there any constraints related to the build process or other factors that explain this choice?

Regards,
Florian.