Re: Plugin Compatibility

So far as I know, anyone writing plugins for RDi has to take into account the version of Eclipse and maybe of Java and finally of the development kit for RDi - you can't rely on anything working completely between releases.

It is what it is, it seems!

HTH
Vern

On 8/23/2016 8:25 AM, Craig Richards wrote:

All,

[ To recap, I’m on RDi 9.5.03, Java 8. I built a simple plugin for
inserting some text etc. I wanted / expected to be able to use the same
plugin on my colleagues machines (RDi 9.1.1, Java 7. ) and hopefully just
be copying the exported jar file to their plugin directory.

It works fine on my RDi 9.5.03 ]

Here is a little more ( albeit inconclusive ) information on this plugin
discussion…

Thomas gave me some interesting advice about removing the minimum Execution
Environment ( basically removing Java 1.8 from the plugin.xml overview tab
) and also taking out any settings in the “Minimum/Maximum Version to
Match” from the Dependencies Tab.

I do understand the implications of doing this, but in my particular narrow
case, I believe I am familiar enough with the environments to which I am
exporting it to accept the risk.

Having done this, ( and reloaded etc ) I found that I could see my plugin
listed on the configuration details screen, but when Eclipse loaded it
listed an error: Class co.uk.greywidget.lpexextensions.InsertDivision not
found.

This just appears as text above the command line in the LPEX Text Editor.

Having browsed around a bit and had a play with the plugin and manifest, I
couldn’t really see what the problem was and so I gritted my teeth and just
built the plugin again with a different version from my old 9.1.1
installation of RDi which matches my colleagues machines.

I was able to export the plugin from this version and copy it to their
plugin directories and it ran fine.

So I don’t know why taking out the dependency stuff works fine on 9.5.03
and allows the plugin to be loaded on 9.1.1 but results in a Class Not
Found error.

And I would like to understand it better as this stuff bugs me a lot <looks
over at Buck> but for now I’ll leave it be.

regards

Craig


On Friday, 19 August 2016, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 8/19/2016 1:22 PM, dlclark@xxxxxxxxxxxxxxxx <javascript:;> wrote:

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx <javascript:;>> wrote on

08/19/2016 12:42:44 PM:

Do you have a link which explains how to make a true plug-in, with
features and an update site and all that for Eclipse 4.4? I'd love to
learn how to do it the approved way! I'm not asking you to search for
me, only if you've got one in front of you! :-)

As I said, I have not tried developing my own plugins for

Eclipse.

Therefore, I do not know exactly how Eclipse handles such things. I

have

only worked with services and plugins for other software and there is
always a "registration" process that is required. So, today, I did a
little bit of reading on the Internet about Eclipse plugins and relayed
the two most pertinent comments I was able to find quickly.

Righty-o, thanks Dave!

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx <javascript:;>
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx <javascript:;>
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.