karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-3102) "New" resolver leaves some bundles in resolved state and install unexpected bundles
Date Sat, 27 Dec 2014 15:59:13 GMT

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

Jean-Baptiste Onofré commented on KARAF-3102:
---------------------------------------------

I noticed another "weird" behavior.

For instance, the openjpa feature depends to the jpa 2.0.0 feature. However, the openjpa feature
installation installs the hibernate-jpa-api bundle which is part of the jpa 2.1.0 feature
(not the 2.0.0):

{code}
karaf@root()> feature:install -v openjpa
Adding features: openjpa/[2.3.0,2.3.0]
Changes to perform:
  Region: root
    Bundles to install:
      mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/1.0.2
      mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint.aries/1.0.4
      mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/1.0.2
      mvn:org.apache.aries.jpa/org.apache.aries.jpa.container.context/1.0.4
      mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.0.1
      mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.1.1
      mvn:commons-collections/commons-collections/3.2.1
      mvn:commons-lang/commons-lang/2.6
      mvn:commons-pool/commons-pool/1.6
      mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/1.1.1
      mvn:org.apache.geronimo.specs/geronimo-jpa_2.0_spec/1.1
      mvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.2
      mvn:org.apache.openjpa/openjpa/2.3.0
      mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_6
      mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-dbcp/1.4_3
      mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.serp/1.14.1_1
      mvn:org.apache.xbean/xbean-asm4-shaded/3.16
      mvn:org.hibernate.javax.persistence/hibernate-jpa-2.1-api/1.0.0.Final
Installing bundles:
  mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/1.0.2
  mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint.aries/1.0.4
  mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/1.0.2
  mvn:org.apache.aries.jpa/org.apache.aries.jpa.container.context/1.0.4
  mvn:org.apache.aries.transaction/org.apache.aries.transaction.blueprint/1.0.1
  mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.1.1
  mvn:commons-collections/commons-collections/3.2.1
  mvn:commons-lang/commons-lang/2.6
  mvn:commons-pool/commons-pool/1.6
  mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/1.1.1
  mvn:org.apache.geronimo.specs/geronimo-jpa_2.0_spec/1.1
  mvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.2
  mvn:org.apache.openjpa/openjpa/2.3.0
  mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_6
  mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-dbcp/1.4_3
  mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.serp/1.14.1_1
  mvn:org.apache.xbean/xbean-asm4-shaded/3.16
  mvn:org.hibernate.javax.persistence/hibernate-jpa-2.1-api/1.0.0.Final
Starting bundles:
  org.apache.openjpa / 2.3.0
  org.apache.aries.jpa.api / 1.0.2
  org.apache.aries.jpa.blueprint.aries / 1.0.4
  org.apache.aries.transaction.manager / 1.1.1
  org.apache.aries.jpa.container.context / 1.0.4
  org.apache.aries.transaction.blueprint / 1.0.1
  org.apache.aries.jpa.container / 1.0.2
Done.
{code}

> "New" resolver leaves some bundles in resolved state and install unexpected bundles
> -----------------------------------------------------------------------------------
>
>                 Key: KARAF-3102
>                 URL: https://issues.apache.org/jira/browse/KARAF-3102
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 4.0.0
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.0.0
>
>
> It seems that the "new" bundle resolver leaves some bundles in resolved state (without
any clear reason).
> For instance, if we install the spring feature:
> {code}
> karaf@root()> feature:install spring
> {code}
> The aries util, aopalliance, ASM bundles stay in resolved state:
> {code}
> karaf@root()> la|grep -i resolved
>  7 | Resolved |  30 | 2.12.0          | JLine                                       
                      
> 19 | Resolved |  20 | 1.1.0           | Apache Aries Util                           
      
> 47 | Resolved |  20 | 5.0.3           | ASM all classes with debug info             
                      
> 50 | Resolved |  30 | 1.0.0.6         | Apache ServiceMix :: Bundles :: aopalliance
> {code}
> These bundles are not fragment, and we start the bundle "by hand", they start without
problem:
> {code}
> karaf@root()> bundle:start 50
> karaf@root()> la|grep -i aopalliance
> 50 | Active   |  30 | 1.0.0.6         | Apache ServiceMix :: Bundles :: aopalliance
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message