This has the side effect that our bundle names look like package names in the message but gives a very clear naming convention. The OSGi resolver algorithm will potentially evaluate lots of different candidate permutations to find a dependency resolution solution.
In some scenarios, the number of permutations can be quite large, but the resolver only throws one exception and cannot easily report on every issue it encountered. Thus, it often just picks an error to report; I believe in the case of the Felix resolver, it reports the last error encountered. In some scenarios, it is not the last error that captures the root cause. This can happen when there are multiple providers of a given package. In that case, it may be reporting an error resolving a provider different than the one you were expecting.
For the Felix resolver, you can get more information if you set the framework log level to 4 i. Then the resolver will log a similar message for each failed permutation. Nice blog post. Regarding the version range issue… this is an unfortunate consequence of the broken version numbering scheme used by Google.
Version 10 is backwards compatible with version 9, and with all previous versions. So they should really be version 1. In that case you would import a range of [1. I started testing with Felix 4. Manifest-Version: 1. Resolver error data. Caused by missing constraint in bundle constraint:.
You are commenting using your WordPress. Page generated in 0. Sign up to our Newsletter A fresh new issue delivered monthly. Eclipse Community Forums. Forum Search:. Tycho build with RAP 2. Fri, 05 July Daria Huber Messages: 14 Registered: June RuntimeException: org. I build with RAP 2. Re: Tycho build with RAP 2. Sat, 06 July Markus Knauer Messages: Registered: July Hi Daria, I don't know the reason of your problem but usually it is connected with the org.
Speaking of changes I'm not aware of any particular problems with this build, but on the other hand I cannot guarantee that it is still working. Maybe it helps to look closer into our build of the RAP examples. Tue, 09 July Hi Markus, thanks for your reply. Tycho build for RAP 2. So I changed my build just like in your example from releng. But it doesn't work.
I get: Failed to execute goal org. My application bundles has project. And only feature and product has a top parent as parent pom. Also I added my bundles to project. Is it still a bug like or my problem is between keypad and a chair? Thanks in advance Report message to a moderator. Thu, 11 July Obviously there's still something wrong but the error message doesn't tell me the real reason.
I'm puzzled. How can we proceed? If MyProject is just one example standalone project and does not include any secret information nor code it may help to attach this project to this newsgroup thread. Hi Markus, I figured out what the problem is. Thanks for your help. I deleted all versions in Manifest under dependecies and I could build war archive for my application. But I think it is not a proper way. I think I have to specify what versions of bundles I want to build with.
I tried to deploy my war archive on a tomcat. But it fails. Bundle org. Missing imported package javax. MF file in the build process. MF header. Developer Developed custom OSGi modules. Example: bnd. Export-Package: com. If the module required package was not exported already in the above procedure then we can see same error. When we use some third-party jars in the modules then we can expect the same error. Solution: 1. If the module required package is from third party library then we need to find OSGi compliance version of same jar and deploy in Liferay Module Framework.
Newer version of third-party libraries are OSGi compliance. MF file with OSGi headers. Example: latest google gson Solution: 2. If the jar was not found as OSGi compliance jar then use includeresource option.
Includeresource option will add jar to module lib directory and add packages in the private package list. Meera Prince. Liferay Contributor of the Year Liferay Top Contributor Award Winner Email This BlogThis! Share to Twitter Share to Facebook. Newer Post Older Post Home. Subscribe to: Post Comments Atom.
0コメント