Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » M2T (model-to-text transformation) » Lost in JET to JET2 migration
Lost in JET to JET2 migration [message #37100] Thu, 29 November 2007 15:58 Go to next message
Paulo Pinto is currently offline Paulo PintoFriend
Messages: 12
Registered: July 2009
Junior Member
Hi everyone,

I have a JET code base that was developed against Eclipse 3.0.

Now I need to make it work under Eclipse 3.3, and found out that JET has
been completely redeveloped and even some tags that we use (<%@include %>)
are no longer supported.

I searched everywhere but failed to find any kind of migration guide. :(

How can I make my templates work under JET2 with the small number of
changes as possible?

Thanks in Advance,
Paulo Pinto
Re: Lost in JET to JET2 migration [message #37442 is a reply to message #37100] Fri, 30 November 2007 14:54 Go to previous message
Paul Elder is currently offline Paul ElderFriend
Messages: 849
Registered: July 2009
Senior Member
Paulo:

First, the original JET is still available, in its original location:

org.eclipse.emf.codegen

There is no need to move to JET2.

JET2 was developed to make templates more accessible to non-technical users.
It features:
* tag-based substitution rather than Java code
* template control (invocation & writing of results) via included tags.
* dynamic loading of JET2 plug-ins into the workbench for execution
(avoiding the need for runtime workbenches).
* an easier to use mechanism for template overriding
It is possible to create code generators with JET without writing any Java
code.

I still do not have a full worked out migration story for JET1 (the original
JET) to JET2.

The 0.8.x JET2 compiler does have a flag to compile JET1 templates and to
generated JET1-compatible Java classes. This supports everything except for
the 'skeleton' and (because of an oversight) the 'nlString' attributes of
<%@jet %>. The JET2 runtime does not, provide a direct equivalent to the
JETEmitter class for dynamic compilation of templates. All this to say that
if you statically load your JET1 templates, and do not use skeleton, you can
switch to the JET2 compiler, if you want.

Moving your templates to JET2 tag libraries is more complex. If your
templates and orchestration code are stable, I honestly cannot see much
reason to migrate.

Please feel free to ask questions. As you say, there isn't currently a
migration guide. Questions and answers may provide the materials to create
one.

Paul



"Paulo Pinto" <pjmlp@progtools.org> wrote in message
news:b1762c68870150a6376a6810736562ff$1@www.eclipse.org...
> Hi everyone,
>
> I have a JET code base that was developed against Eclipse 3.0.
>
> Now I need to make it work under Eclipse 3.3, and found out that JET has
> been completely redeveloped and even some tags that we use (<%@include %>)
> are no longer supported.
>
> I searched everywhere but failed to find any kind of migration guide. :(
>
> How can I make my templates work under JET2 with the small number of
> changes as possible?
>
> Thanks in Advance,
> Paulo Pinto
>
Previous Topic:NullPointer
Next Topic:Will JMerge be part of M2T?
Goto Forum:
  


Current Time: Fri Apr 26 17:32:38 GMT 2024

Powered by FUDForum. Page generated in 0.03017 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top