karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ciprian Ciubotariu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4930) karaf-maven-plugin verify mojo fails
Date Wed, 06 Dec 2017 22:51:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281062#comment-16281062
] 

Ciprian Ciubotariu commented on KARAF-4930:
-------------------------------------------

>From your build log I see you are using the version where this does not fail: {{karaf-maven-plugin:4.0.5:verify}}.
Here is the excerpt from the pom.xml:

{noformat}
        <!-- working: -->
        <karaf.version>4.0.5</karaf.version>

        <!-- failing: -->
        <!--<karaf.version>4.0.6</karaf.version>-->
        <!--<karaf.version>4.0.7</karaf.version>-->
        <!--<karaf.version>4.0.8</karaf.version>-->

        <!-- working: -->
        <!--<karaf.version>4.1.0-SNAPSHOT</karaf.version>-->
{noformat}

I've rerun this against the new released karaf versions and here is the result:
* 4.0.9: failed
* 4.1.0 - 4.1.3: success
* 4.2.0.M1: success

To summarize, only the 4.0.x series exhibits this problem. One can workaround this by using
the last working version of the plugin to verify features, i.e. 4.0.5. Not sure if this qualifies
as a fix, but... that's the state of affairs.

> 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.6, 4.0.7, 4.0.8
>            Reporter: Ciprian Ciubotariu
>            Priority: Minor
>
> The feature verify mojo consistently fails with:
> {noformat}
> 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)))"\
>     ]\
>   ]\
> ]
> {noformat}
> 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.4.14#64029)

Mime
View raw message