[
https://issues.apache.org/jira/browse/MYFACES-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908898#action_12908898
]
Leonardo Uribe commented on MYFACES-2911:
-----------------------------------------
FM >> in this case it's not clear to me why you have an API and IMPL bundle at
all.
The idea of have an API and IMPL bundle is provide a "common point", so
different implementations share the same classes/methods, but that does not
means it is possible to setup, for example Mojarra API with Myfaces IMPL and
viceversa.
FM >> It there a specific reason why this is different in MyFaces?
In fact, the same is true for Mojarra. Note API and IMPL are not released
separately.
I'll close this issue as invalid. At this point it is clear and specific
version of API requires a specific version of IMPL, so the manifest entry is
correct.
> 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.
