[
https://issues.apache.org/jira/browse/MYFACES-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Mittag reopened MYFACES-2911:
-----------------------------------
I think I understand now why you have the entry, but this restriction seems to
be more a logical one than a useful constraint if you run inside an OSGi
environment.
First, the API bundle will run with all versions of IMPL greater than 2.0.1
anyway, because Require-Bundle:
org.apache.myfaces.core.impl;bundle-version="2.0.1" only says that 2.0.1 is the
minimal required version (otherwise it would be [2.0.1, 2.0.1]).
Second, if I create my own extended IMPL version of myfaces and name it
myversion.core.impl it will not run.
Third, I have described an usage scenario (see issue Trindidad-1901) where I
"reuse" the API bundle and the IMPL is simply not visible to the API bundle.
I think if you provide an OSGi version of MYFACES you should consider the usage
scenarios which are typical in this environment.
Frank
> OSGi Manifest: MyFaces API Bundle requires IMPL Bundle
> ------------------------------------------------------
>
> Key: MYFACES-2911
> URL: https://issues.apache.org/jira/browse/MYFACES-2911
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Environment: OSGi container
> Reporter: Frank Mittag
> Priority: Minor
>
> The MANIFEST.MF file of the org.apache.myfaces.core.api bundle/jar contains
> the entry:
> Require-Bundle: org.apache.myfaces.core.impl;bundle-version="2.0.1"
> So the API bundle requires the IMPL bundle to work. This is not needed and
> prevents scenarios where the e.g. two IMPL bundles just reference the same
> API bundle.
> The easiest solution is just to remove the entry.
> Frank
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
