Ciprian Ciubotariu created KARAF-4930:
-----------------------------------------
Summary: karaf-maven-plugin verify mojo fails
Key: KARAF-4930
URL: https://issues.apache.org/jira/browse/KARAF-4930
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 4.0.8, 4.0.7, 4.0.6
Reporter: Ciprian Ciubotariu
Priority: Minor
The feature verify mojo consistently fails with:
{{Message: Unable to resolve root: missing requirement [root] osgi.identity;
osgi.identity=karaf-bug; type=karaf.feature; version=1.0.0.SNAPSHOT;
filter:="(&(osgi.identity=karaf-bug)(type=karaf.feature)(version>=1.0.0.SNAPSHOT))"
[caused by: Unable to resolve karaf-bug/1.0.0.SNAPSHOT: missing requirement
[karaf-bug/1.0.0.SNAPSHOT] osgi.identity; osgi.identity=shell;
type=karaf.feature; version="[4.0.8,4.0.8]" [caused by: Unable to resolve
shell/4.0.8: missing requirement [shell/4.0.8] osgi.identity;
osgi.identity=org.apache.karaf.shell.core; type=osgi.bundle;
version="[4.0.8,4.0.8]"; resolution:=mandatory [caused by: Unable to resolve
org.apache.karaf.shell.core/4.0.8: missing requirement
[org.apache.karaf.shell.core/4.0.8] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.osgi.service.cm)(version>=1.5.0)(!(version>=2.0.0)))"]]]}}
This started off with version 4.0.6 and propagated to the latest stable 4.0.8,
but feature validation still works fine with 4.1.0-SNAPSHOT. I bisected the
problem to commit 2d96f914, which seems to be related to KARAF-884.
Use this simple project here to reproduce:
https://github.com/CMoH/karaf-feature-verify-bug
>From my understanding the failing feature.xml files contain a primary feature,
>while those where verification works correctly do not. Would it be appropriate
>to add a flag that allows devs to direct karaf-maven-plugin not to add that
>primary feature? For now the only workaround I found is to enumerate all other
>features by hand for the verify mojo, which is cumbersome and error-prone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
