Barışcan Güngör wrote:
Now the problem is in maven3 (m2eclipse) it gives a warning that says “version must be a constant instead of a variable”.
A POM deployed to a repository must be self-contained in the way that all information required to process it (e.g. calculate the effective POM) must be present in the POM.
This does not hold for a POM referencing its parent via an external property. Until Maven provides support to (partly) interpolate properties before deployment, using properties for POM coordinates is an anti-pattern that enables deployment of broken POMs, i.e. that can't be used during dependency resolution as we have already seen in the past for stuff in central.
Regarding easier version maintenance for multi-module projects, right now I can only suggest to use the Release Plugin and to vote for MNG-624.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
