This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Unable to run a felix osgi bundle with my API | ||
---|---|---|---|
Product: | projects | Reporter: | karamba84 |
Component: | Maven OSGi bundles | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P1 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Windows 7 x64 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
karamba84
2013-11-18 09:25:01 UTC
apparently felix cannot cope with the inter-project links created with Compile on Save turned on. We replace the repository jars with target/classes folders (effectively simulating a reactor build) that's where file:/G:/data/code/soundbox/SoundBox-CoreLibrary/target/classes/ comes from. Disabling CoS on the project (or all projects) should help http://wiki.netbeans.org/FaqCompileOnSave#Using_Compile_on_Save_in_Maven_Projects Thanks. But now i get another error/warning. When i run my application, it does not go into the activator.java When i create a new maven osgi bundle, i get: main: [propertyfile] Creating new property file: C:\Users\oli\Documents\NetBeansProjects\Test\target\run.properties [java] org.osgi.framework.BundleException: Unresolved constraint in bundle org.dyndns.soundi.SoundBox-API [1]: Unable to resolve 1.0: mERROR: Bundle org.dyndns.soundi.SoundBox-API [1] Error starting file:/C:/Users/oli/.m2/repository/org/dyndns/soundi/SoundBox-APIissing requirement [1.0] osgi.wiring.package; (osgi.wiring.package=org.dyndns.soundi.soundboxcorelibrary) [java] at org.apache.felix./1.0-SNAPSHOT/SoundBox-API-1.0-SNAPSHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.dyndns.sounframework.Felix.resolveBundleRevision(Felix.java:3974) [java] at org.apache.felix.framework.Felix.startBundle(Felix.java:2037) [java] at odi.SoundBox-API [1]: Unable to resolve 1.0: missing requirement [1.0] osgi.wiring.package; (osgi.wiring.package=org.dyndns.soundrg.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291) [java] at org.apache.felix.framework.FrameworkStartLevelImpl.runi.soundboxcorelibrary)) [java] hi [java] (FrameworkStartLevelImpl.java:304) [java] at java.lang.Thread.run(Thread.java:744) So the output is pretty messed up. Also, i dont understand whats now wrong. Because the API has no activator and no dependency (except the OSGi one). Should i file a new bug or do you see whats wrong? (In reply to karamba84 from comment #2) > Thanks. But now i get another error/warning. > When i run my application, it does not go into the activator.java > When i create a new maven osgi bundle, i get: > > main: > [propertyfile] Creating new property file: > C:\Users\oli\Documents\NetBeansProjects\Test\target\run.properties > [java] org.osgi.framework.BundleException: Unresolved constraint in > bundle org.dyndns.soundi.SoundBox-API [1]: Unable to resolve 1.0: mERROR: > Bundle org.dyndns.soundi.SoundBox-API [1] Error starting > file:/C:/Users/oli/.m2/repository/org/dyndns/soundi/SoundBox-APIissing > requirement [1.0] osgi.wiring.package; > (osgi.wiring.package=org.dyndns.soundi.soundboxcorelibrary) > [java] at org.apache.felix./1.0-SNAPSHOT/SoundBox-API-1.0-SNAPSHOT.jar > (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.dyndns.sounframework.Felix.resolveBundleRevision(Felix.java:3974) > [java] at org.apache.felix.framework.Felix.startBundle(Felix.java:2037) > [java] at odi.SoundBox-API [1]: Unable to resolve 1.0: missing > requirement [1.0] osgi.wiring.package; > (osgi.wiring.package=org.dyndns.soundrg.apache.felix.framework.Felix. > setActiveStartLevel(Felix.java:1291) > [java] at > org.apache.felix.framework.FrameworkStartLevelImpl.runi.soundboxcorelibrary)) > [java] hi > [java] (FrameworkStartLevelImpl.java:304) > [java] at java.lang.Thread.run(Thread.java:744) > > So the output is pretty messed up. Also, i dont understand whats now wrong. > Because the API has no activator and no dependency (except the OSGi one). > Should i file a new bug or do you see whats wrong? The output being message up is unfortunately outside of our hands. when spawning the maven build JVM, we use ProcessBuilder.redirectErrorStream(true); call to make sure error and std outputs are merged on the side of the process for us. So it's either the jdk messing up, or more likely the maven plugin/ant task executing. In terms what the error means, I'm not sure, it looks like some dependency bundles are missing or a version mismatch. That no longer appears to be netbeans codebase related though. |