Eclipse Community Forums: Visual Editor (VE) » Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2

Home » Archived » Visual Editor (VE) » Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2

Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2 [message #20743]

Thu, 26 February 2004 07:26

Eclipse User

We have a plug-in for WSAD 5.0.1 (and Visual Editor) which we would like
to port to Eclipse 2.1.2 and VE 0.5.0.

Is there any documentation about the migration path one needs to take?

Will the subsequent port to Eclipse 3.0 and VE 1.0 be a big step?

Thanks

- Janak
janak.mulani@canoo.com

Re: Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2 [message #20824 is a reply to message #20743]

Thu, 26 February 2004 12:57

Eclipse User

Janak,

I've just posted such a migration path in the previous thread "Adding new
Beans to the Palette"

Tell me if it's what you're looking for.

Regarding Eclipse 3.0 and VE 1.0 I think you could have a look at the plugin
files to see how deeply they changed (that's what I'm going to do anyway,
I'll keep you posted)

Sebastien.

"janak" <janak.mulani@canoo.com> wrote in message
news:c1komh$no8$1@eclipse.org...
>
> We have a plug-in for WSAD 5.0.1 (and Visual Editor) which we would like
> to port to Eclipse 2.1.2 and VE 0.5.0.
>
> Is there any documentation about the migration path one needs to take?
>
> Will the subsequent port to Eclipse 3.0 and VE 1.0 be a big step?
>
> Thanks
>
> - Janak
> janak.mulani@canoo.com
>
>
>

Re: Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2 [message #21331 is a reply to message #20824]

Fri, 27 February 2004 05:15

Eclipse User

Sebastien,

Many thanks.

Actually just after doing yesterday's post I set about changing Joe's
palette example for Eclipse 2.1.2. And I made all the changes (to xml and
xmi) that you have listed in your solution.

I ran Joe's example palette in WSAD 5.0.1 and it ran fine.

I then ran the "changed for Eclipse example palette" but it does not run
because it is not able to find the Bean Jars (even after setting the
variable). It seems the Classpath specification has changed between WSAD
5.0.1 and Eclipse 2.1.2. To make the Eclipse example run I had to
explicitly include the bean jars in the build path.

Have you experienced this?
(I am taking the liberty to send my Eclipse plug-in to you for
verification, pl install and run it if you have time.)

> Tell me if it's what you're looking for.

Sure this helps and as said earlier I did the same after posting my query.
But it takes lot of groping around and ends up in taking a path that
perhaps others have already taken.

So it would help a lot if:

1. There is a global picture of what all needs to change.
2. And info about the semantics of change and specifics where possible.

> Regarding Eclipse 3.0 and VE 1.0 I think you could have a look at the plugin
> files to see how deeply they changed (that's what I'm going to do anyway,
> I'll keep you posted)

Thanks.

Actually what I meant was is it a good idea to go to Eclipse 2.1.2 and VE
0.5.0 from WSAD 5.0.1 or should we go to Eclipse 3.0 and VE 1.0.0?

- Janak

Re: Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2 [message #21339 is a reply to message #21331]

Fri, 27 February 2004 08:52

Eclipse User

Originally posted by: richkulp.NO.SPAM.us.ibm.com

You can go to 0.5.0 and from there to the current 1.0.0. The override
files are the same format at this time for 0.5.0 and 1.0.0, however, in
the next few weeks we are stepping up to the EMF Opensource version of
the override files (from our private internal version), which is a
different format. However, since we have to do the conversion ourselves
of our many files, I'm going to see about writing a conversion utility
to convert the 1.0.0 current format to the new format. And I'll put this
utility out on the VEP site when ready.

--
Thanks, Rich Kulp

Re: Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2 [message #21460 is a reply to message #20824]

Thu, 26 February 2004 13:23

Eclipse User

Ok I've just looked at the plugin files :
- Few differences in plugin manifest files (just more required plugins)
- No differences in the palette XMI files

So I assume the palette plugins for VE 0.5.0 will work like a charm with VE
1.0.0

Anybody in the VE team could confirm it ?

"S

Re: Migration of plug-in from WSAD 5.0.1 to Eclipse 2.1.2 [message #21482 is a reply to message #21331]

Mon, 01 March 2004 04:12

Eclipse User

Janak,

I've ran your plugin and it works fine for me (no classpath problem, and no
need to add the jars manually, the variable does the job)
The only problem you could have is if you installed the VE Examples plugin
(it contains the wizzowidget example) so there would be 2 WIZZO_WIDGETS
variable and it does not work very well (actually you could not use the
variable at all).

So I renamed the variable to WIZZO_WIDGETS_PORT in your plugin definition
and it works fine.

The XMI looks good to me.

I send you the modified plugin.xml file (you don't need it if you haven't
installed VE Examples).

Hope that helps,

Sebastien.

"janak" <janak.mulani@canoo.com> wrote in message
news:c1n5b8$nae$1@eclipse.org...
> Sebastien,
>
> Many thanks.
>
> Actually just after doing yesterday's post I set about changing Joe's
> palette example for Eclipse 2.1.2. And I made all the changes (to xml and
> xmi) that you have listed in your solution.
>
> I ran Joe's example palette in WSAD 5.0.1 and it ran fine.
>
> I then ran the "changed for Eclipse example palette" but it does not run
> because it is not able to find the Bean Jars (even after setting the
> variable). It seems the Classpath specification has changed between WSAD
> 5.0.1 and Eclipse 2.1.2. To make the Eclipse example run I had to
> explicitly include the bean jars in the build path.
>
> Have you experienced this?
> (I am taking the liberty to send my Eclipse plug-in to you for
> verification, pl install and run it if you have time.)
>
>
> > Tell me if it's what you're looking for.
>
> Sure this helps and as said earlier I did the same after posting my query.
> But it takes lot of groping around and ends up in taking a path that
> perhaps others have already taken.
>
> So it would help a lot if:
>
> 1. There is a global picture of what all needs to change.
> 2. And info about the semantics of change and specifics where possible.
>
> > Regarding Eclipse 3.0 and VE 1.0 I think you could have a look at the
plugin
> > files to see how deeply they changed (that's what I'm going to do
anyway,
> > I'll keep you posted)
>
> Thanks.
>
> Actually what I meant was is it a good idea to go to Eclipse 2.1.2 and VE
> 0.5.0 from WSAD 5.0.1 or should we go to Eclipse 3.0 and VE 1.0.0?
>
> - Janak
>
>
>