Community
Participate
Working Groups
Build Identifier: Version: Indigo Service Release 1 Build id: 20110916-0149 Virgo Tooling Version 1.0.0.201110312003-SNAPSHOT Regardless of what type of project is created (EclipseRT Bundle, Spring Bundle, Spring with OSGi nature installed) any exported packages from bundle A cannot be imported into bundle B. The manifest editor seems to find the exported packages ok and allows their selection however once added to the manifest, tooling reports that the package cannot be resolved. For additional info, please see Eclipse forum entry: http://www.eclipse.org/forums/index.php/mv/msg/285975/793713/ Reproducible: Always Steps to Reproduce: 1. Create two bundle projects 2. Create a package in each project 3. Create a class in each project 4. Export package(s) in manifest.mf 5. Import package in only one project 6. Save manifest.mf and error should appear. I've basically be trying to create a virgin project for use with Virgo and ran into this problem. From the assistance I have received in the Virgo forums it has been identified as a bug. For additional info, please see Eclipse forum entry: http://www.eclipse.org/forums/index.php/mv/msg/285975/793713/
Marking as critical, since you really can't use the tooling in a meaningful way without this.
OK, this ended up being invalid. In order to establish a dependency between Virgo bundles you need to be using a par project. You can also do this with plans, but it is unlcear to me right now how that would work, as it seems that you would have to deploy the dependency to the server in order to actually use it.
Please note that an alternative to a PAR is to use a plan, but note that the tooling support for plans is currently rather rudimentary.
