Messages

1

Automation Interface, Add-Ins and Tools / Re: Reverse engineer with MDG Link to Eclipse

« on: August 04, 2006, 06:03:53 am »

That's a little messed up that you need to workaround that way. My guess is that EA needs to make a new Jar compatible with 3.2's plugin changes.

2

Automation Interface, Add-Ins and Tools / Re: Reverse engineer with MDG Link to Eclipse

« on: August 03, 2006, 08:24:01 pm »

I did an experiment and I found that MDG Link works with Eclipse 3.2 if I install Eclipse 3.2 fresh and didn't do any additional plugin configuration stuff besides adding in the MDG Link jar.

If you want to approach it that way you can. Just download the whole thing over again, install MDG Link jar, verify that everything works as needed, and then incrementally use find and discover features / manually install your old features and plugins until you're all set up again.

Personally, I plan on zipping up my functioning version at work and bringing it home since it's pretty much identical to what I use at home.

3

Automation Interface, Add-Ins and Tools / Re: Reverse engineer with MDG Link to Eclipse

« on: August 03, 2006, 07:29:55 am »

Well, it's odd. I just tried it at work and my work 3.2 config seems to be different than my home 3.2 config because it was able to connect and recognize my workspace.

I'm wondering if it's a feature I have at home that I don't have at work that's causing problems or perhaps vice versa. When I get home tonight I will try connecting to 3.1 again just as a proof of concept and then see what I can do to my 3.2 settings to get the thing talking properly with MDG Link.

4

Automation Interface, Add-Ins and Tools / Re: Reverse engineer with MDG Link to Eclipse

« on: August 03, 2006, 06:58:35 am »

Daemon, I am getting the same error. Unfortunately, I just bought MDG Link and when I did the free trial I was using Eclipse 3.1.

Since there was nothing on the MDG Link for Eclipse that said it wasn't compatible with Eclipse 3.2, I bought it (in fact, it states that it is compatible with 3.x).

My guess is that the JAR they're using for Eclipse does not work for 3.2 and they need to make a new JAR.

I haven't seen any indication of an acknowledgment of this problem yet or heard any timetable for a fix and I'm a little concerned that I may have just blown $100 on a broken product.