Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » M2T (model-to-text transformation) » minimal jet plugin
minimal jet plugin [message #39225] Fri, 11 January 2008 01:53 Go to next message
Eclipse UserFriend
Originally posted by: ymo.noemail.com

Hi.

1) We want to ship the transformation as a standaalone RCP app. It does
not have to have a ui at all. Obviously we dont want to ship eclipse as
is. It will be a waste of resources. I understand we can run a
transformation using the eclipse ant runner. Is there some samples
explaining how the product file can be done to generate the branded
eclipse rcp ?

2) What is the minimal set of plugins required to run a transformation ?

3) Our generator generates java code. We also want to compile this
generated code somehow. Maybe the ant runner is enough assuming we can get
a hand of the location of the jdk. But i am not sure how you would call
ant from whithin an ant transformation.
Re: minimal jet plugin [message #39348 is a reply to message #39225] Fri, 11 January 2008 15:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ymo.noemail.com

Just for clarifications we want to ship the jet transformations runtime
only. This is not meant for crating new templates. Its just to run the
already compiled transformations. My understanding is that we need an
eclipse like environment even to run the jet transformations.
Re: minimal jet plugin [message #39846 is a reply to message #39348] Tue, 15 January 2008 14:44 Go to previous messageGo to next message
Paul Elder is currently offline Paul ElderFriend
Messages: 849
Registered: July 2009
Senior Member
I'm working on it. Right now, all of JET is bound-up into one plug-in which
won't load on RCP.

BTW, do you have the Eclipse workspace (org.eclipse.core.runtime.resources)
in your RCP application, or are you expecting to write to file system paths?

Paul

"ymo" <ymo@noemail.com> wrote in message
news:2dac54a6c19b4f369e5eee41d9fef689$1@www.eclipse.org...
> Just for clarifications we want to ship the jet transformations runtime
> only. This is not meant for crating new templates. Its just to run the
> already compiled transformations. My understanding is that we need an
> eclipse like environment even to run the jet transformations.
>
Re: minimal jet plugin [message #41042 is a reply to message #39846] Fri, 25 January 2008 13:48 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ymo.noemail.com

Hi Paul.

I can ship the whole sdk files as it is if i cant do it otherwise. I don't
have a restriction to only ship an RCP. So, for now i can ship whatever is
required to make jet transformations run. But the question was more like
what is the minimal set of plugins required ? Is the platform jars good
enough ? Do you need emf on top ? What do you need as a minimum ?

So if you can you can just go over :
1) How to create a jet plugin from scratch.
2) How to create the .product file to produce a standalone packaged jet
transformation and share it with us.


Thanks.
Re: minimal jet plugin [message #41166 is a reply to message #41042] Thu, 31 January 2008 15:34 Go to previous message
Paul Elder is currently offline Paul ElderFriend
Messages: 849
Registered: July 2009
Senior Member
Ymo:

A JET Transformation has a dependency on the org.eclipse.jet plug-in. Here
is a partial dependency tree.

org.eclipse.jet
org.eclipse.jet.core
org.eclipse.text - used for buffering expanded templates
org.eclipse.core.commands
org.eclipse.equinox.common
org.eclipse.ant.core - used for ant tasks
org.eclipse.core.resourse - used for workspace tags + JET builder
org.eclipse.core.rutnime - IStatus, IProgressMonitor, ...
org.eclipse.emf.common - some internal use
org.eclipse.emf.codegen - JMerge (java:merge tag)
org.eclipse.emf.ecore - Used for handling EMF input models
org.eclipse.emf.ecore.xmi - Used for loading EMF input models
org.eclipse.core.expressions - ?
org.eclipse.core.filebuffers - Used by by workspace tags
org.eclipse.jdt.core - Used for java:* tags
org.apache.ant - Used by JET Ant tasks
org.eclipse.ui - optional - used to hook in team APIs with UI.

As for packaging for deployment, JET transformations are plug-ins, and can
be deployed as such. The best mechanism for plug-in deployment is to use
features. So, build a feature that includes your JET plug-in.

I am not an expert in packaging features into a product. But, I think the
starting point is likely to be features.

Paul
"ymo" <ymo@noemail.com> wrote in message
news:96188e8f34c6f7f01bd73b06a6c0128b$1@www.eclipse.org...
> Hi Paul.
>
> I can ship the whole sdk files as it is if i cant do it otherwise. I don't
> have a restriction to only ship an RCP. So, for now i can ship whatever is
> required to make jet transformations run. But the question was more like
> what is the minimal set of plugins required ? Is the platform jars good
> enough ? Do you need emf on top ? What do you need as a minimum ?
>
> So if you can you can just go over :
> 1) How to create a jet plugin from scratch.
> 2) How to create the .product file to produce a standalone packaged jet
> transformation and share it with us.
>
>
> Thanks.
>
Previous Topic:Re: JUnit Test on JET Transform
Next Topic:UnitTest for custom tags
Goto Forum:
  


Current Time: Fri Apr 26 00:49:43 GMT 2024

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

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

Back to the top