On 10/31/06, Steinar Bang <[EMAIL PROTECTED]> wrote:
>>>>> "Tom Huybrechts" <[EMAIL PROTECTED]>:
> You can create a 'target platform' directory which contains all the jars
of
> plugins you use. Then set this directory in Preferences > PDE > Target
> platform. You will have to add ALL the plugins you use, even the core
> eclipse plugins.
> But later you can just add stuff here and press reload on the same
> preference page.
Ok. Thanx! Now I'm able to add it as a required plug-in in an RCP
project. But I'm still not able to list its exported package when
clicking "Add.." in "Imported Packages" in the RCP project.
I can think of two things:
- you have already added it as a required bundle. Remove it, and try to add
an imported package again
- there is something wrong with the export-package header. Open your plugin
in the 'Plugins'-view and check the manifest.
Here's what I did (this is eclipse-3.2 on Ubuntu Dapper):
- Did the commands:
mkdir $HOME/ecplise_pde_plugins
cd $HOME/ecplise_pde_plugins
(cd /usr/local/eclipse-3.2; tar cf - plugins) | tar xf -
- Selected Window->Preferences... from the menus
- Open "Plug-in Development" and select "Target Platform"
- In the "Location" field clicked on "Browse..." and browsed to the
$HOME/ecplise_pde_plugins directory
That made all of the recular plug-ins show up.
Then I dropped in an OSGi bundle, clicked on "Reload", and as you
said, the plug-in showed up.
> You could even create a POM for your target platform that copies
> everything from the maven repo.
> If you go for the second option, you will probably no longer have a
> PDE project and will lose the PDE's support for running OSGi
> applications.
Quite.
Thanx for the solution! :-)
I'm not sure this is the solution I'll eventually want (I'm not happy
with having a copy of the eclipse platform, and mixing the platform
plug-ins with something particular to one project), but it gives me a
fallback.
I only keep the platform and thirdparty plugins in the target platform, and
it is checked into SVN. All other projects come as source projects.
Especially if you work in teams, an additional advantage is that you will
not be dependent on the Eclipse version a developer happens to be using - so
you can try out the latest 3.3 milestone while still developping against
3.2...
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
