[ 
https://issues.apache.org/jira/browse/FELIX-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard S. Hall closed FELIX-1300.
----------------------------------

    Resolution: Fixed

I have committed this change. For people who really do not want to create new 
cache's, we could look into creating a script that renames the embedded/ 
directory in bundleX/versionY.0/ to bundle.jar-embedded/.

> Remove legacy bundle cache support when extracting embedded JAR files
> ---------------------------------------------------------------------
>
>                 Key: FELIX-1300
>                 URL: https://issues.apache.org/jira/browse/FELIX-1300
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: felix-1.8.1
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: felix-2.0.0
>
>
> A while ago we modified IContent so we could use that interface to extract 
> JAR files, which was necessary for fragment support where we needed to be 
> able to access embedded content to construct the host class path. The 
> approach is actually more powerful than what is necessary, since we allow JAR 
> files to be extracted from embedded JAR files and JAR files embedded in the 
> embedded JAR files to be extracted and so. As a result of this, you can end 
> up with situation where embedded JAR files in different embedded JAR files 
> may have the same name, so to avoid name clashes, we extract embedded JAR 
> files into a directory named after the bundle. This was problematic at the 
> top-level, since it would not be backwards compatible with existing caches. 
> As a result, we special case the top-level and just use the name "embedded" 
> for the directly as was done in the past. With the move to 2.0, I want to 
> remove this legacy since there isn't much point to keeping it.

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

Reply via email to