| Using Apache Collections in plugin development [message #257901] |
Mon, 09 June 2008 16:18  |
Eclipse User |
|
|
|
Originally posted by: pzs.dcs.gla.ac.uk
I've posted about this before, but my posts seem to have disappeared. I
also don't think this is really "newcomer", but I can't work out the
bewildering array of Eclipse mailing lists.
I'm developing an Eclipse plugin that relies on the excellent Jung graph
library. If I link the Jung jar files, it does not work - I need to
convert the Jung source into a plugin itself, and include this. That
removes the first layer of Jung errors, but then I get errors Jung's
dependencies are missing, including the Apache commons collections15
libraries.
I've tried making a dummy plugin project that includes the commons15 jar
as an export, but this doesn't work.
Is there anything else I can try? Can I download the collection15
libraries as a plugin as an Eclipse package?
Thanks,
Peter
|
|
|
| Re: Using Apache Collections in plugin development [message #257925 is a reply to message #257901] |
Mon, 09 June 2008 20:42  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Peter Saffrey wrote:
> I've posted about this before, but my posts seem to have disappeared. I
> also don't think this is really "newcomer", but I can't work out the
> bewildering array of Eclipse mailing lists.
>
> I'm developing an Eclipse plugin that relies on the excellent Jung graph
> library. If I link the Jung jar files, it does not work - I need to
> convert the Jung source into a plugin itself, and include this. That
> removes the first layer of Jung errors, but then I get errors Jung's
> dependencies are missing, including the Apache commons collections15
> libraries.
> I've tried making a dummy plugin project that includes the commons15 jar
> as an export, but this doesn't work.
>
> Is there anything else I can try? Can I download the collection15
> libraries as a plugin as an Eclipse package?
There is no rule that says you have to package JARs that you depend on
as separate plugins. They can be included in your own plugin if you
want. As far as I can tell, the only reasons to package libraries as
separate plugins is to allow them to be shared across differen plugins,
and/or to be able to update them separately from the "real" plugin(s).
If neither of those is important to you, you can just embed the JARs in
your plug project and then add them to the Classpath of your plugin (in
the Classpath section, Runtime tab of the manifest/plugin.xml editor).
Hope this helps,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.10294 seconds
] 
Search
Help
Register
Login
Home
