Managing Your Target Platform with Virgo Tooling [message #967540] |
Thu, 01 November 2012 17:07  |
Eclipse User |
|
|
|
Software
Eclipse Juno SR 1 20120920-0800
Virgo 1.0.0.201209050002-RELEASE
I'm embarking on a project to move an product built with Eclipse PDE to Virgo. Previously we built our own target platform folder with an ant script and P2. Now it seems with Virgo Tooling that the target platform is implicitly defined by defining your Virgo Server and associating it with your Bundle Project. At first I imported our existing PDE projects and then added the 'OSGI Bundle Project Nature' to them. I was running into lots of issues resolving dependencies so I deleted all the projects and defined a new Bundle Project. I'm adding classes one by one from the old PDE project to the new Bundle Project. I'm running into two issues. First my Virgo server seems to have two locations for resolving dependencies, the usr and ext folders in the repository. As I run into an external dependency I've been copying the bundle to the usr folder of the repository. This seems to work fine for resolving dependencies but I don't know how to force Eclipse to refresh after adding new bundles to the folder. They seem to show up after quite awhile but I don't know what triggers Eclipse into recognizing that there are new bundles in the Virgo repository. Second I'm unable to resolve packages exported by org.eclipse.osgi and am wondering what is the best way to fix that.
So I have three questions:
Is there a way to convert PDE projects to Bundle projects?
Is there a way to refresh Eclipse's view of Virgo's repository folders.
I'm not finding packages exported from the org.eclipse.osgi bundle. It is present in Virgo's plugins directory but that is not exposed via the Virgo Server definition. What is the best way to pick up those exports.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.26868 seconds