-
-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export of bndrun fails but existing and calculated runbundles are identical #4082
Comments
NB the same bug exists in 5.1.0-SNAPSHOT and 5.0.0. |
Sorry the bug is not quite reproducible as described, I missed the resolve step (though the error message from the export is very misleading). I still think there is a problem but it manifests in a more complex project, I will try again to produce a reproducible example. |
Even without changing the version from 4.1.0 to 5.2.0, I get an error when running the
Tested with (
@njbartlett : can you explain what you mean with "I missed the resolve step" |
I found my solution in eclipse-osgi-technology/osgi.enroute#99, as explained in the linked documentation the OSGi Resolving step is needed. With maven:
This adds following lines to the diff --git a/app/app.bndrun b/app/app.bndrun
index 1b66a66..d66d3ed 100644
--- a/app/app.bndrun
+++ b/app/app.bndrun
@@ -6,4 +6,7 @@ index: target/index.xml;name="app"
-runfw: org.eclipse.osgi
-runee: JavaSE-1.8
--resolve.effective: active
\ No newline at end of file
+-resolve.effective: active
+-runbundles: \
+ org.apache.felix.scr;version='[2.1.10,2.1.11)',\
+ org.example.impl;version='[1.0.0,1.0.1)' |
I agree with @njbartlett here.
The |
Fixes: bndtools#4082 Signed-off-by: Jeremie Bresson <jeremie.bresson@unblu.com>
The issue is fixed with version
|
Bnd 5.0.1 cannot build the enRoute Quickstart project.
I created a sample project as follows:
I edited
pom.xml
to change<bnd.version>4.1.0</bnd.version>
to5.0.1
and then ranmvn clean verify
and it failed on the export goal:Note that the existing and calculated runbundles list are identical.
The text was updated successfully, but these errors were encountered: