Do not use compile dependency for embedded code 73/37073/4
authorRobert Varga <rovarga@cisco.com>
Mon, 4 Apr 2016 13:26:22 +0000 (15:26 +0200)
committerRobert Varga <rovarga@cisco.com>
Mon, 4 Apr 2016 14:31:53 +0000 (16:31 +0200)
commita034bf9bbc7abef6a749b9ed658d74a90cea1a0e
treefcfbd34a0b1e68c43aab4ff66eae090a1bd4418e
parentff2b6259f1c980966d87f6f4403dab9800cc245a
Do not use compile dependency for embedded code

We are embedding xtend and its dependencies into our jar and using
compile dependency means karaf plugin will download the jars as it
will see it as a runtime dependency.

Degrade the dependency to scope=provided, as we will provide the
dependencies by our own jar. This breaks maven-xtend-plugin, which
needs guava<15 and relies on it being pulled in transitively. Fix that
by adding an explitic dependency in plugin declaration.

Change-Id: Idb358bca4ce8eab7179d6867e603dd6b2306e732
Signed-off-by: Robert Varga <rovarga@cisco.com>
binding/mdsal-binding-generator-impl/pom.xml
common/parent/pom.xml