[jira] Issue Comment Edited: (FELIX-2067) Fragment bundle ignored silently when the host Bundle-SymbolicName equals import package name

["Richard S. Hall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832855#action_12832855 ] 

Richard S. Hall edited comment on FELIX-2067 at 2/12/10 6:03 AM:
-----------------------------------------------------------------

This issue was being caused by the new code for aggregating host/fragment dependencies. It needed to handle different types of dependencies (e.g., host, bundle, package) separately, but it was merging them all together. This allowed requirements with the same target name (e.g., bundle symbolic, package name) to interfere with each other, causing the requirements to be calculated incorrectly.

I have committed a patch for this issue against the trunk for any further maintenance releases to Framework 2.0.x. However, I verified that this bug was not introduced into the Framework 3.0.0 code in my sandbox. I plan to move my sandbox code to trunk shortly. So, I am currently undecided about how to handle this issue.

      was (Author: rickhall):
    This issue was being caused by the new code for aggregating host/fragment dependencies. It needed to handling different types of dependencies (e.g., host, bundle, package) separately, but it was merging them all together. This allowed requirements with the same target name (e.g., bundle symbolic, package name) to interfere with each other, causing the requirements to be calculated incorrectly.

I have committed a patch for this issue against the trunk for any further maintenance releases to Framework 2.0.x. However, I verified that this bug was not introduced into the Framework 3.0.0 code in my sandbox. I plan to move my sandbox code to trunk shortly. So, I currently am undecided about how to handle this issue.
  
> Fragment bundle ignored silently when the host Bundle-SymbolicName equals import package name
> ---------------------------------------------------------------------------------------------
>
>                 Key: FELIX-2067
>                 URL: https://issues.apache.org/jira/browse/FELIX-2067
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-2.0.3
>         Environment: ANY
>            Reporter: Guo Du
>            Assignee: Richard S. Hall
>             Fix For: felix-3.0.0
>
>         Attachments: testbundles.zip
>
>
> I reproduce the problem with two simple bundles. Attachment is the test bundles.
> The test case export a package org.bug.api and import by itself.
> Fail silently When the host Bundle-SymbolicName=org.bug.api
> Success When the host Bundle-SymbolicName=org.bug.apix
> It may caused the name used as key for maps.
> ====================================================================
> FAILURE
> ====================================================================
> -> install file:/tmp/fail/bug.bundle.fragment-0.0.1-SNAPSHOT.jar
> Bundle ID: 3
> -> install file:/tmp/fail/bug.bundle.host-0.0.1-SNAPSHOT.jar
> Bundle ID: 4
> -> start 4
> -> ps
> [   3] [Installed  ] [    1] Unnamed -
> org.bug:bug.bundle.fragment:bundle:0.0.1-SNAPSHOT (0.0.1.SNAPSHOT)
> [   4] [Active     ] [    1] Unnamed -
> org.bug:bug.bundle.host:bundle:0.0.1-SNAPSHOT (0.0.1.SNAPSHOT)
> ====================================================================
> EXPECTED
> ====================================================================
> -> install file:/tmp/success/bug.bundle.fragment-0.0.1-SNAPSHOT.jar
> Bundle ID: 3
> -> install file:/tmp/success/bug.bundle.host-0.0.1-SNAPSHOT.jar
> Bundle ID: 4
> -> start 4
> DEBUG: WIRE: 4.0 -> org.osgi.framework -> 0
> DEBUG: FRAGMENT WIRE: 3.0 -> hosted by -> 4.0
> -> ps
> [   3] [Resolved   ] [    1] Unnamed -
> org.bug:bug.bundle.fragment:bundle:0.0.1-SNAPSHOT (0.0.1.SNAPSHOT)
> [   4] [Active     ] [    1] Unnamed -
> org.bug:bug.bundle.host:bundle:0.0.1-SNAPSHOT (0.0.1.SNAPSHOT)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.