Re: [tycho-user] Best practice for version handling

[Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>]

Parent coordinates have to be constants, otherwise Maven will not be
able to load build extensions that provide Tycho-specific behaviour. The
same probably applies to artifactId and packaging, but I am not 100% sure.

I do not believe there are any fundamental restrictions on other parts
of pom.xml, but implementation may or may not be possible without
changes to Maven core. Other Maven tools, like m2e, will likely need
changes to support the new properties.

The real question, though, is it worth the trouble?

--
Regards,
Igor

On 12-01-09 4:03 AM, Mickael Istria wrote:
> Regarding this issue, would it be possible to have Maven support a
> ${manifest.bundle-version} - and other ${manifest.*} property or
> something like that ?
> This would be a convenient way to avoid duplication of data between
> Manifest and pom. What is the opinion of Maven experts about this idea,
> especially, is this doable given the Maven internal axioms?
>
> On 08/01/2012 13:20, Robert Gründler wrote:
> > Hi,
> >
> > whenever i update the version number of one of my features, i have to
> > manually increment the version tag in each of the poms, otherwise tycho
> > throws an "does not match Maven version" error.
> >
> > As this is quite tedious, i'm wondering how others handle this version
> > problem.
> >
> > regards
> >
> >
> > -robert