On 01/02/18 15:26, Stephen Kitt wrote: > On Thu, 1 Feb 2018 15:11:07 +0100 > Michael Vorburger <vorbur...@redhat.com> wrote: >> On Thu, Feb 1, 2018 at 12:50 PM, Robert Varga <n...@hq.sk> wrote: >>> The project does not list a dependency on mdsal-model-sources, hence >>> that artifact is not built in autorelease until after the archetype: >> So where would we best add these dependencies we need to "help" Maven >> figure out the dependency tree correctly? Are we saying we need to >> (today and remember in the future...) put everything that the >> archetype needs into a <dependencies> in >> controller/opendaylight/archetypes/pom.xml ? > Heh, this is what we discussed in the kernel call a couple of weeks > ago: we ultimately need to move the archetype out of controller... (Or > is this already the simplified archetype?) > > However in this case, yes, we probably need additional mdsal > dependencies in the archetype (which is OK since controller depends on > mdsal anyway).
... so essentially you need to scope=test dependencies which are used by the test, which includes all base ODL artifacts referenced by whatever the artifact generates. I suspect this will end up being a short list due to transitive dependencies. Bye, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
