Re: [m2t-dev] What's the difference between Xpand and Acceleo?

[Cédric Brun <cedric.brun@xxxxxxx>]

Hi,

Looks like you're speaking about Acceleo from Acceleo.org and not the
M2T/Acceleo on Eclipse.org :
http://www.eclipse.org/modeling/m2t/?project=acceleo

The later is a brand new implementation started from scratch and has
been standalone *from the beginning*, unlike the former implementation.
With this new implementation this should be quite easy to tackle, when
you create a new module a Java class is generated being your module
"API", ou just have to use this Java class and you're done. But you're
right about the former implementation : using it in standalone mode was
not easy and had a number of limitations.

Anyway the newsgroup is a better place for such questions :
http://www.eclipse.org/forums/index.php?t=thread&frm_id=24&S=8dfe059d084560be46baea8e6e9b3811

Cheers,

Cédric

K J a écrit :
> My thanks to everyone for the responses.
>
> Cedric - I believe you are right that it shouldn't take much effort to
> push things forward. Perhaps the only real problem(s) is that I can't
> find sufficient documentation to help me use Acceleo standalone, or
> I'm misunderstanding the purpose of a standalone project. I haven't
> done much with Acceleo beyond working with chains that someone else
> created, so maybe it's obvious to more experienced users. I've tried
> performing exports several different ways, and half the time I end up
> with an empty project. Once I have an exported project (which includes
> a src directory with .java and .emt files, a project jar containing
> .class and .mt files, and a lib directory with an assortment of other
> dependencies such as fr.obeo.acceleo.ecore.jar, etc.), I'm not really
> sure what to do next. Does a standalone project give me the context
> (i.e. classpath dependencies) to launch a chain from the command-line,
> or is it just providing a single Java class per template which I could
> string together using Java or a script? How is it intended to be used?
> Any guidance you can give me would be greatly appreciated.
>
> Thanks again.
>
>
> On Thu, Dec 3, 2009 at 12:21 AM, Cédric Brun <cedric.brun@xxxxxxx> wrote:
>   
>> Hi,
>>
>> As Karsten said Acceleo and XPand are both model to text transformation
>> technologies and as such answer the same needs. One big difference
>> between them is the fact that M2T/Acceleo is an implementation of the
>> OMG Standard for Model To Text transformation whereas XPand has it's own
>> ocl-like in-house syntax.
>>
>> Concerning the Maven issue I'm quite interested in getting more
>> information about what would be "missing".  As M2T/Acceleo is standalone
>> - it can be used as plain old Java jar without the Eclipse/OSGi runtime
>> I have the feeling we  probably don't need much effort to push things
>> forward. What do you mean by "play nice with Maven" ?
>>
>> Cédric
>>
>> K J a écrit :
>>     
>>> Not sure where I should be posting this question, so I apologize if
>>> this isn't the appropriate forum.
>>>
>>> Some people at my company have been using Acceleo for a while now, and
>>> I've been looking for ways to make it play nice with Maven (so far
>>> without luck). During my research I came across the M2T project and
>>> subsequently Xpand. I've been trying to figure out the differences
>>> between Acceleo and Xpand, but I'm not clear on what they each do. It
>>> seems like there is a lot of overlap between the two projects, and if
>>> that is true, I don't understand why they are both part of M2T. Can
>>> someone please clarify?
>>>
>>> Thanks in advance.
>>> _______________________________________________
>>> m2t-dev mailing list
>>> m2t-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/m2t-dev
>>>
>>>
>>>       
>> _______________________________________________
>> m2t-dev mailing list
>> m2t-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2t-dev
>>
>>     
> _______________________________________________
> m2t-dev mailing list
> m2t-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2t-dev
>
>