JET transforms must run with-in Eclipse. Your non-Eclipse plug-in Java
project does not satisfy this requirement - when you launch the Java
program, it gets its own JRE, which does not include the essentail Eclipse
bits.

I am working on re-factoring JET so that some sort of Eclipse-free behaviour
is possible, but I cannot promise immediate results - there is still much
work to do. Some examples of the dependencies JET still has one Eclipse:

1) dynamic loading of JET projects is done through OSGi. This will not
change, but for a Java program without OSGi, it should be possible to at
least run a JET template by creating a JET2Context and JET2Writer and
instantiating the Java class created by the JET compiler and calling the
generate() method. I'm close on this, but it requires the removal of some
deprecated methods on JET2Writer.

2) Many JET tags (ws:file, ws:project, ...) have dependencies on the Eclipse
workspace. It should be possible to have versions of these that work just
with java.io.File, but this is not done yet.

3) Several JET tags make use of the org.eclipse.text plug-in and, in
particular the IDocument interface. JET 0.8.0 has started to refactor some
of this, but still it is not perfect.

Can JET run in a Eclipse - RCP environment (so thus outside of eclipse) ?

"Paul Elder" <pelder@ca.ibm.com> wrote in message
news:f057ou$j41$1@build.eclipse.org...
> BlankAlberto:
>
> Short answer:
>
> JET Transforms must be launched from an Eclipse plug-in.
>
> More detailed answer:
>
> JET transforms must run with-in Eclipse. Your non-Eclipse plug-in Java
> project does not satisfy this requirement - when you launch the Java
> program, it gets its own JRE, which does not include the essentail Eclipse
> bits.
>
> I am working on re-factoring JET so that some sort of Eclipse-free
> behaviour is possible, but I cannot promise immediate results - there is
> still much work to do. Some examples of the dependencies JET still has one
> Eclipse:
>
> 1) dynamic loading of JET projects is done through OSGi. This will not
> change, but for a Java program without OSGi, it should be possible to at
> least run a JET template by creating a JET2Context and JET2Writer and
> instantiating the Java class created by the JET compiler and calling the
> generate() method. I'm close on this, but it requires the removal of some
> deprecated methods on JET2Writer.
>
> 2) Many JET tags (ws:file, ws:project, ...) have dependencies on the
> Eclipse workspace. It should be possible to have versions of these that
> work just with java.io.File, but this is not done yet.
>
> 3) Several JET tags make use of the org.eclipse.text plug-in and, in
> particular the IDocument interface. JET 0.8.0 has started to refactor some
> of this, but still it is not perfect.
>
> Paul
>
>
>