[
https://issues.apache.org/jira/browse/MYFACES-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997722#comment-12997722
]
Jakob Korherr commented on MYFACES-3044:
----------------------------------------
Adding this to the export packages of the maven-bundle-plugin configuration
should fix this issue:
META-INF.internal-resources.javax.faces;version="${project.version}",
META-INF.resources;version="${project.version}",
META-INF.services;version="${project.version}"
However, I am not sure if this is the expected thing to do here. Is anyone here
more familiar with OSGi?
> Resource jsf.js not found when using the OSGi bundle
> ----------------------------------------------------
>
> Key: MYFACES-3044
> URL: https://issues.apache.org/jira/browse/MYFACES-3044
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.3
> Reporter: Clovis
>
> First there is a
> WARNING: Resource referenced by resourceName jsf.js and libraryName
> javax.faces not found in call to ResourceHandler.createResource. It will be
> silenty ignored.
> and later a NullPointerException
> Using javax.faces.PROJECT_STAGE=Development, the class loader was trying to
> load META-INF/internal-resources/javax.faces/jsf-uncompressed-full.js (so I
> added the "package" META-INF.internal-resources.javax.faces to the list of
> exported packages of myfaces-bundle.jar). But then I changed it from
> Development to Production, and myfaces tried to load something else (and I
> decided to write a bug).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
