[mvn] Use ${project.version} instead of hard-coded references

[kthoms]

Some POMs contain redundant information on the used Xtext version, e.g. xtext-core/releng/pom.xml

		<dependency>
			<groupId>org.eclipse.xtext</groupId>
			<artifactId>org.eclipse.xtext</artifactId>
			<version>2.15.0-SNAPSHOT</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.xtext</groupId>
			<artifactId>org.eclipse.xtext</artifactId>
			<version>2.15.0-SNAPSHOT</version>
			<classifier>sources</classifier>
		</dependency>

The version 2.15.0-SNAPSHOT can be replaced by ${project.version}.

This makes the changeset smaller when changing versions.

[cdietrich]

Surr the publishing Project can handle that ?

[kthoms]

What's so special about the publishing project? You mean the CI job?
That's quite a usual style in MVN. It is a simple variable substitution.

[cdietrich]

i mean that typefox thingy that pushes the stuff to soanytype and maven central.
e.g. in out maven plugins we need to uplicate stuff from parent poms.

[LorenzoBettini]

When this #2231 is implemented there'll be no need to use versions at all (and I hope that it won't break publishing ;)

[kthoms]

At least you would have to specify the BOM's version, which again is the project version. It is just less dependencies listed.

[LorenzoBettini]

yes!

[cdietrich]

p2 gen is removed now. to be tested: can publish plugin handle it without explicit version

[cdietrich]

see also #2135