Karaf distribution by default uses user local m2 repository,
which may be poluted by locally built artefacts.

This may introduce heisen bugs and confuse users / developers, since distribution they downloaded
is not run with artefacts, which was shipped in build (e.g. collected by integration project)
but artefacts from user local maven repository.

In local repository I had md-sal-config snapshot with following metadata

distribution-karaf-0.2.0-SNAPSHOT/system/org/opendaylight/controller/md-sal-config/maven-metadata-local.xml

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>org.opendaylight.controller</groupId>
<artifactId>md-sal-config</artifactId>
<versioning>
<versions>
<version>1.1-SNAPSHOT</version>
</versions>
<lastUpdated>20140810104953</lastUpdated>
</versioning>
</metadata>

Karaf comes bundled with

distribution-karaf-0.2.0-SNAPSHOT/system/org/opendaylight/controller/md-sal-config/maven-metadata-local.xml

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>org.opendaylight.controller</groupId>
<artifactId>md-sal-config</artifactId>
<versioning>
<versions>
<version>1.1-SNAPSHOT</version>
</versions>
<lastUpdated>20140910025023</lastUpdated>
</versioning>
</metadata>

Feature install used local artefact from local m2 repository which was invalid in context of downloaded distribution (artefacts in distribution required different configuration).

When I wiped local .m2 repository, extracted same build, did feature:install for same component, it used correct (bundled) artefact.

Fix for this is to separate user m2 repository and m2 repository used by karaf.