|User Library not visible in project [message #1006839]
||Sat, 02 February 2013 13:06
| Ulrich Schmidt
Registered: January 2013
I've added Equinox to "Window-Preferences-Java-BuildPath-UserLibraries" as "External Jar" under the Name "Equinox". But when trying to add it to a specific Java Project by:|
BuildPath-AddLibraries the name "Equinox" is not seen in the list of choosable libraries.
I'm running Eclipse Juno Service Release 1 and Windows 7 Home.
Any idea what might be wrong?
|Re: User Library not visible in project [message #1007029 is a reply to message #1007028]
||Mon, 04 February 2013 01:53
| Ed Merks
Registered: July 2009
When working with OSGi in Eclipse, if there are external libraries you
need and aren't already made available as bundles in your PDE target
platform, you generally put them in a project with a PDE nature, ensure
that you put those libraries on the runtime path (via the MANIFEST.MFs
Runtime tab's Classpath) and that you export the packages you want to be
visibe to other bundles (via the Runtime tab's Exported Packages). Once
you've done that, in every project where you want to use those
libraries, you use the MANIFEST.MF's Dependencies tab to either
specified your Required Plug-ins or the Imported Packages. This is how
you specify what the bundles make available and what they require be
available at runtime. From this information the PDE can automatically
compute your classpath for development time. With this approach you
never manage the classpath manually, you only manage the Runtime and the
Dependencies of your MANIFEST.MFs. It's totally convenient and I use
this approach even when I'm not developing plug-ins. I'll continue to
suggest you do the same.
On 04/02/2013 7:33 AM, Ulrich Schmidt wrote:
> Sorry I phrased these words without really thinking. You are not
> rigth. In the MANIFEST.MF you the the OSGi-Server the RunPath you
> need. The BuildPath still has to be defined to your development
> enviroment; either explicitely the complete CLASSPATH for compiling
> with javac or implicitely as BuildPath in you IDE (for editing and
> Ulrich Schmidt wrote on Sun, 03 February 2013 15:34
>> You are right, OSGi dependencys are defined in the MANIFEST-file, I
>> don't doubt this. ...
Powered by FUDForum
. Page generated in 0.06089 seconds