Rework version artifact version tracking 45/11845/13
authorRobert Varga <rovarga@cisco.com>
Wed, 8 Oct 2014 22:26:58 +0000 (00:26 +0200)
committerRobert Varga <rovarga@cisco.com>
Tue, 14 Oct 2014 09:58:03 +0000 (11:58 +0200)
commitff74fdbb200a48843d7ec9168fa9e9ffe6a74fa4
treedbc51ff1640d7bc449c6456460a1de8dfcc46768
parenta46ecf5a96ae1f721bd87c39e44ab55cf9b34b71
Rework version artifact version tracking

This patch reworks the way we track our internal artifacts by moving the
definitions from the aprent pom into a dedicated yangtools-artifacts
versions.

This artifact's dependencyManagement section is then imported into the
parent. This may look unnecessary, but it allows our downstream users to
import the same file and have the versioning work.

An interesting side-effect of that is that the properties cannot be
relied on carrying versions of artifacts and then be picked up by the
features.xml file.

This patch fixes that by introducing a script into the build cycle,
which looks at a template features.xml and resolves the versions as
currently visible in the dependency tree of the artifact.

Change-Id: I193586f777478c12520358b9909cfb61e40d14b4
Signed-off-by: Robert Varga <rovarga@cisco.com>
Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
code-generator/pom.xml
common/artifacts/pom.xml [new file with mode: 0644]
common/features-builder/pom.xml
common/features/pom.xml
common/parent/pom.xml
common/pom.xml
integration-test/bug1196-test-model/pom.xml
integration-test/bundle-test/pom.xml
model/ietf/pom.xml