Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: AW: [jwt-dev] jwt editor installation

Hi Charles,

Have you installed missing plug-ins such as EMF, GEF, draw2d in your Eclipse? You can verify it in your Help > Software Updates > manage configuration whether they are available.
It is possible that Ganymede JEE does not include EMG, GEF & co...

Good luck
Mickael

Souillard Charles a écrit :
Hi all,

sorry for my next stupid question but I am not able to install my JWT env correctly... I have installed ganymede (jee developpers version) + TPTP and downloaded the three projects (up to date of this morning):
- we : 9866 errors
- transformation-base : 16 errors
- xpdl : no error
I have successfully installed we editor thanks to update site.
I have tried with jdk 1.5 and jdk 1.6 and error nb is the same.
Errors are concerning emf, gef, draw2d...
I don't understand because I have for example emf.commmon in my plugins directory but the package is not found in eclipse java editor...

Is it that there is a conflict between ganymede and my eclipse or is it an environment pb on my side ?

thanks for your help.
Charles

Marc Dutoo a écrit :
Hi

JWT CVS HEAD currently requires Eclipse 3.4 platform (new tabbed properties extension), and will work indiferently on JDK 1.5 or 6 .

I'm currently working on updating JWT CVS to Ganymede in the METAMODELEXT branch, migrated EMF templates already works and there's just a few issues with icons to check.

Christian, I agree quite a few things have changed, and because of the same reasons I also approve Ganymede being a requirement.

Regards,
Marc

Christian Saad a écrit :
Hi,

jwt-we 0.4.0 works well on Eclipse 3.3, it does not require 3.4. Also, as
Mickael wrote, a JRE 5 should be sufficient.
There seem to be, in fact, some problems concerning Ganymede since some
parts of the API have changed, e.g. the handling of files (opening, saving).
However, there is currently some work on the way to adapt jwt-we to
Ganymede. I think, that this could become an obligatory requirement in the future as it probably would be very challenging to support both APIs at the
same time and some new features of 3.4 are very handy.

Regards,
Christian

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev







Back to the top