Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [m2t-dev] Move backend to m2t.core?

From my point of view, one is enough.

I think the idea was to have one more internal kind of thing and another thing with contains common tools like jmerge or the recipes framework. However I think m2t common is enough.

 

Bernd

 

 

 

 

 

Mit freundlichen Grüßen

Bernd Kolb

(b.kolb@xxxxxxxxxxx)

http://www.kolbware.de

 

--

KolbWare

(Beratung & Coaching)

Bernd Kolb

Franz-Marc Str. 35

89520 Heidenheim

 

Mobil: 0163/7321605  

 

From: m2t-dev-bounces@xxxxxxxxxxx [mailto:m2t-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Elder
Sent: Monday, February 04, 2008 4:23 PM
To: Model to Text
Subject: Re: [m2t-dev] Move backend to m2t.core?

 


As Sven has replied. The component name is m2t.common. But, I'm for it. Also, I wonder whether we really need m2t.common AND m2t.shared. Their purposes are very similar. Thoughts?

Paul

Paul Elder
IBM Rational Software
Tel: +1-613-599-3916 (until Feb 18, 2008)
Tel: +1 613-270-4560 (after Feb 18, 2008)
E-mail: pelder@xxxxxxxxxx



Arno Haase <arno.haase@xxxxxxxxxxxxxxxxxxxx>
Sent by: m2t-dev-bounces@xxxxxxxxxxx

2008-02-01 10:14 AM

Please respond to
Model to Text <m2t-dev@xxxxxxxxxxx>

To

Model to Text <m2t-dev@xxxxxxxxxxx>

cc

Subject

[m2t-dev] Move backend to m2t.core?

 




Hi all,

the backend development is progressing nicely. And it is intended as
part of a common infrastructure that integrates all m2t languages, so I
think it should be moved to m2t.core.

Any opinions on this?

- Arno


--
Arno Haase
Langemarckstr. 16
53227 Bonn

Mobil: +49 160 98525085
Tel:   +49 228 9654443
Fax:   +49 228 9654448

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


Back to the top