Add scope to maven dependency key
Different versions could be defined for compile/runtime scope in
the dependency management block.
This is for example how Gradle publishes dependency constraints
to <dependencyManagement> for the same dependency with different
versions in a Java Library:
Signed-off-by: Jendrik Johannes <firstname.lastname@example.org>
15 Dec 17 a82cf4ac0b40d25cb12218df669be14259f9a675
Make sure that published component attributes can also be mutated
This commit adds support for serialization of component level attributes. Before, the module metadata descriptor
could contain attributes, but since we never used them, apart from the hard-coded `status` attribute, there was
no need to serialize them in binary format. Now, it is possible for a consumer to overwrite component attributes,
including custom attributes. This makes necessary for serializing this information.
However, this commit does NOT add support for publishing component attributes: at this point, while there's a way
to _consume_ attributes, there's no way to _publish_ them.
14 Dec 17 57d81b52934ed1e40bff933bb5200e64afc85d3b