![]() An Import-Package should still work by specifying the attribute. However this doesn't stop you from using any packages from misc. There would be no way to distinguish between the identical packages (one from core, and one from misc), so you would always get wired to one but not the other. If the attributes are the same in both recipes then it would be no different than having no attributes. core could use for example " core=split mandatory:=core" on exported > value in both manifests generated by recipe > I think problem is mandatory attribute. > bundle is suggested by official API doc: (In reply to Dawid Pakula from comment #3) Īt .Module.start(Module.java:444)Īt .ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634)Īt .ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1613)Īt .ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585)Īt .ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528)Īt .ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)Īt .(EventManager.java:230)Īt .eventmgr.EventManager$n(EventManager.java:340) Unable to resolve resource because it exports package '' and is also exposed to it from resource via the following dependency chain: ResolutionException: Uses constraint violation. Bundle was not resolved because of a uses contraint violation. Unresolved requirement: Require-Bundle: bundle-version="6.1.0" ![]() As the result these plugins can't be used in Photon, example error log:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |