On Tue, Dec 28, 2010 at 2:19 PM, Bernd Fondermann <[email protected]> wrote: > ok, then either spec-compliance can go, too
spec-compliance is marked as optional (since it's not strictly needed by downstream users), which means it won't be a transitive dependency and needs to be declared in downstream modules. Some more on this can be found at: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html - or it is nowhere in the parent > tree. Does the module declaration in vysper-parent count? The once in the parent are in a <dependencyManagement> which means they are not actually set up as dependencies. Instead, they are defined with their properties (primarily version) so that when used (such as on vysper-core), we need not include their version (or other stuff) everywhere. Typically used for versions and exclusions of transitive dependencies. This is documented here: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > Maven-agnostic thanks, Fun, isn't it ;-) /niklas
