Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » M2T (model-to-text transformation) » [Acceleo] Problems with Builder in Kepler
[Acceleo] Problems with Builder in Kepler [message #1090707] Tue, 20 August 2013 14:29 Go to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Dear all,

I am migrating our software from Indigo to Kepler and I encountered the
following error when trying to build the Acceleo project:

Errors occurred during the build.
Errors running builder 'Acceleo Builder' on project 'xxx'.
The feature 'et(Parameter)' is not a valid feature

As a result I do not have an output files generated.

I cannot interpret this error message at all. Again, the very same project
worked in Indigo.

Thanks for any help in advance
Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1090768 is a reply to message #1090707] Tue, 20 August 2013 16:06 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4110
Registered: July 2009
Senior Member
Hi

This is the missing first letter problem. "Set(Parameter)" would have
been sensible.

Something somewhere has got a byte offset and it causes chaos. The
problem eventually goes away once you rebuild everything enough times.
I've not managed to work out where the inconsistency is.

Try cleaning, restarting, wiping the bin folders with your OS, switch
backwards and forwards between binary/ASCII emtl files, changing JRE to
some other version and back again, make sure your Kepler compiler
preferences are the same as on Indigo ...

Regards

Ed Willink


On 20/08/2013 15:29, Marc-Florian Wendland wrote:
> Dear all,
>
> I am migrating our software from Indigo to Kepler and I encountered
> the following error when trying to build the Acceleo project:
>
> Errors occurred during the build.
> Errors running builder 'Acceleo Builder' on project 'xxx'.
> The feature 'et(Parameter)' is not a valid feature
>
> As a result I do not have an output files generated.
>
> I cannot interpret this error message at all. Again, the very same
> project worked in Indigo.
>
> Thanks for any help in advance
> Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1413035 is a reply to message #1090768] Wed, 27 August 2014 16:01 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Hi all,

I eventually figured out the reason why the first character gets lost. It
has nothing to do whatsoever with Acceleo compiler settings, encoding
scheme, Eclipse or Java version or XMI parsing. The very reason for this is
a technical deficiency of Acceleo to load/work with metamodels that are
located in the workspace and not deployed in the Eclipse instance. After
removing each and every reference to a locally available metamodel (I simply
deployed the metamodels in my development environment) everything is fine
with Acceleo.

I debugged the location were the first character (in my case, instead of
TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:

org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
uriFragmentSegment), lines 507 and 511

In line 551, the first character is actually cut off.

Again, this problem does not occur if one only worked with deployed models
in the Acceleo modules. Any reference to a locally deployed model is
problematic.

Is this a known issue? Shall I add a critical (I really think such
fundamental issue is critical to Acceleo) Bugzilla for this problem.

Best regards,
Marc-Florian


"Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...

Hi

This is the missing first letter problem. "Set(Parameter)" would have
been sensible.

Something somewhere has got a byte offset and it causes chaos. The
problem eventually goes away once you rebuild everything enough times.
I've not managed to work out where the inconsistency is.

Try cleaning, restarting, wiping the bin folders with your OS, switch
backwards and forwards between binary/ASCII emtl files, changing JRE to
some other version and back again, make sure your Kepler compiler
preferences are the same as on Indigo ...

Regards

Ed Willink


On 20/08/2013 15:29, Marc-Florian Wendland wrote:
> Dear all,
>
> I am migrating our software from Indigo to Kepler and I encountered the
> following error when trying to build the Acceleo project:
>
> Errors occurred during the build.
> Errors running builder 'Acceleo Builder' on project 'xxx'.
> The feature 'et(Parameter)' is not a valid feature
>
> As a result I do not have an output files generated.
>
> I cannot interpret this error message at all. Again, the very same project
> worked in Indigo.
>
> Thanks for any help in advance
> Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1413036 is a reply to message #1090768] Wed, 27 August 2014 16:01 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Hi all,

I eventually figured out the reason why the first character gets lost. It
has nothing to do whatsoever with Acceleo compiler settings, encoding
scheme, Eclipse or Java version or XMI parsing. The very reason for this is
a technical deficiency of Acceleo to load/work with metamodels that are
located in the workspace and not deployed in the Eclipse instance. After
removing each and every reference to a locally available metamodel (I simply
deployed the metamodels in my development environment) everything is fine
with Acceleo.

I debugged the location were the first character (in my case, instead of
TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:

org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
uriFragmentSegment), lines 507 and 511

In line 551, the first character is actually cut off.

Again, this problem does not occur if one only worked with deployed models
in the Acceleo modules. Any reference to a locally deployed model is
problematic.

Is this a known issue? Shall I add a critical (I really think such
fundamental issue is critical to Acceleo) Bugzilla for this problem.

Best regards,
Marc-Florian


"Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...

Hi

This is the missing first letter problem. "Set(Parameter)" would have
been sensible.

Something somewhere has got a byte offset and it causes chaos. The
problem eventually goes away once you rebuild everything enough times.
I've not managed to work out where the inconsistency is.

Try cleaning, restarting, wiping the bin folders with your OS, switch
backwards and forwards between binary/ASCII emtl files, changing JRE to
some other version and back again, make sure your Kepler compiler
preferences are the same as on Indigo ...

Regards

Ed Willink


On 20/08/2013 15:29, Marc-Florian Wendland wrote:
> Dear all,
>
> I am migrating our software from Indigo to Kepler and I encountered the
> following error when trying to build the Acceleo project:
>
> Errors occurred during the build.
> Errors running builder 'Acceleo Builder' on project 'xxx'.
> The feature 'et(Parameter)' is not a valid feature
>
> As a result I do not have an output files generated.
>
> I cannot interpret this error message at all. Again, the very same project
> worked in Indigo.
>
> Thanks for any help in advance
> Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1413037 is a reply to message #1090768] Wed, 27 August 2014 16:02 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Hi all,

I eventually figured out the reason why the first character gets lost. It
has nothing to do whatsoever with Acceleo compiler settings, encoding
scheme, Eclipse or Java version or XMI parsing. The very reason for this is
a technical deficiency of Acceleo to load/work with metamodels that are
located in the workspace and not deployed in the Eclipse instance. After
removing each and every reference to a locally available metamodel (I simply
deployed the metamodels in my development environment) everything is fine
with Acceleo.

I debugged the location were the first character (in my case, instead of
TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:

org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
uriFragmentSegment), lines 507 and 511

In line 551, the first character is actually cut off.

Again, this problem does not occur if one only worked with deployed models
in the Acceleo modules. Any reference to a locally deployed model is
problematic.

Is this a known issue? Shall I add a critical (I really think such
fundamental issue is critical to Acceleo) Bugzilla for this problem.

Best regards,
Marc-Florian


"Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...

Hi

This is the missing first letter problem. "Set(Parameter)" would have
been sensible.

Something somewhere has got a byte offset and it causes chaos. The
problem eventually goes away once you rebuild everything enough times.
I've not managed to work out where the inconsistency is.

Try cleaning, restarting, wiping the bin folders with your OS, switch
backwards and forwards between binary/ASCII emtl files, changing JRE to
some other version and back again, make sure your Kepler compiler
preferences are the same as on Indigo ...

Regards

Ed Willink


On 20/08/2013 15:29, Marc-Florian Wendland wrote:
> Dear all,
>
> I am migrating our software from Indigo to Kepler and I encountered the
> following error when trying to build the Acceleo project:
>
> Errors occurred during the build.
> Errors running builder 'Acceleo Builder' on project 'xxx'.
> The feature 'et(Parameter)' is not a valid feature
>
> As a result I do not have an output files generated.
>
> I cannot interpret this error message at all. Again, the very same project
> worked in Indigo.
>
> Thanks for any help in advance
> Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1413038 is a reply to message #1090768] Wed, 27 August 2014 16:02 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Hi all,

I eventually figured out the reason why the first character gets lost. It
has nothing to do whatsoever with Acceleo compiler settings, encoding
scheme, Eclipse or Java version or XMI parsing. The very reason for this is
a technical deficiency of Acceleo to load/work with metamodels that are
located in the workspace and not deployed in the Eclipse instance. After
removing each and every reference to a locally available metamodel (I simply
deployed the metamodels in my development environment) everything is fine
with Acceleo.

I debugged the location were the first character (in my case, instead of
TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:

org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
uriFragmentSegment), lines 507 and 511

In line 551, the first character is actually cut off.

Again, this problem does not occur if one only worked with deployed models
in the Acceleo modules. Any reference to a locally deployed model is
problematic.

Is this a known issue? Shall I add a critical (I really think such
fundamental issue is critical to Acceleo) Bugzilla for this problem.

Best regards,
Marc-Florian


"Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...

Hi

This is the missing first letter problem. "Set(Parameter)" would have
been sensible.

Something somewhere has got a byte offset and it causes chaos. The
problem eventually goes away once you rebuild everything enough times.
I've not managed to work out where the inconsistency is.

Try cleaning, restarting, wiping the bin folders with your OS, switch
backwards and forwards between binary/ASCII emtl files, changing JRE to
some other version and back again, make sure your Kepler compiler
preferences are the same as on Indigo ...

Regards

Ed Willink


On 20/08/2013 15:29, Marc-Florian Wendland wrote:
> Dear all,
>
> I am migrating our software from Indigo to Kepler and I encountered the
> following error when trying to build the Acceleo project:
>
> Errors occurred during the build.
> Errors running builder 'Acceleo Builder' on project 'xxx'.
> The feature 'et(Parameter)' is not a valid feature
>
> As a result I do not have an output files generated.
>
> I cannot interpret this error message at all. Again, the very same project
> worked in Indigo.
>
> Thanks for any help in advance
> Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1413064 is a reply to message #1413038] Wed, 27 August 2014 17:34 Go to previous messageGo to next message
Ed Willink is currently offline Ed Willink
Messages: 4110
Registered: July 2009
Senior Member
Hi

Well-debugged.

A few users have encountered this.

It's certainly really irritating when it happens, but it does seem to go
away after enough rebuild/re-install cycles, so perhaps only major.

Absolutely worth a Bugzilla.

Regards

Ed Willink



On 27/08/2014 17:02, Marc-Florian Wendland wrote:
> Hi all,
>
> I eventually figured out the reason why the first character gets lost. It
> has nothing to do whatsoever with Acceleo compiler settings, encoding
> scheme, Eclipse or Java version or XMI parsing. The very reason for this is
> a technical deficiency of Acceleo to load/work with metamodels that are
> located in the workspace and not deployed in the Eclipse instance. After
> removing each and every reference to a locally available metamodel (I
> simply
> deployed the metamodels in my development environment) everything is fine
> with Acceleo.
>
> I debugged the location were the first character (in my case, instead of
> TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:
>
> org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
>
> uriFragmentSegment), lines 507 and 511
>
> In line 551, the first character is actually cut off.
>
> Again, this problem does not occur if one only worked with deployed models
> in the Acceleo modules. Any reference to a locally deployed model is
> problematic.
>
> Is this a known issue? Shall I add a critical (I really think such
> fundamental issue is critical to Acceleo) Bugzilla for this problem.
>
> Best regards,
> Marc-Florian
>
>
> "Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...
>
> Hi
>
> This is the missing first letter problem. "Set(Parameter)" would have
> been sensible.
>
> Something somewhere has got a byte offset and it causes chaos. The
> problem eventually goes away once you rebuild everything enough times.
> I've not managed to work out where the inconsistency is.
>
> Try cleaning, restarting, wiping the bin folders with your OS, switch
> backwards and forwards between binary/ASCII emtl files, changing JRE to
> some other version and back again, make sure your Kepler compiler
> preferences are the same as on Indigo ...
>
> Regards
>
> Ed Willink
>
>
> On 20/08/2013 15:29, Marc-Florian Wendland wrote:
>> Dear all,
>>
>> I am migrating our software from Indigo to Kepler and I encountered the
>> following error when trying to build the Acceleo project:
>>
>> Errors occurred during the build.
>> Errors running builder 'Acceleo Builder' on project 'xxx'.
>> The feature 'et(Parameter)' is not a valid feature
>>
>> As a result I do not have an output files generated.
>>
>> I cannot interpret this error message at all. Again, the very same
>> project
>> worked in Indigo.
>>
>> Thanks for any help in advance
>> Marc-Florian
>
Re: [Acceleo] Problems with Builder in Kepler [message #1413370 is a reply to message #1090768] Thu, 28 August 2014 11:17 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Hi all,

I eventually figured out the reason why the first character gets lost. It
has nothing to do whatsoever with Acceleo compiler settings, encoding
scheme, Eclipse or Java version or XMI parsing. The very reason for this is
a technical deficiency of Acceleo to load/work with metamodels that are
located in the workspace and not deployed in the Eclipse instance. After
removing each and every reference to a locally available metamodel (I simply
deployed the metamodels in my development environment) everything is fine
with Acceleo.

I debugged the location were the first character (in my case, instead of
TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:

org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
uriFragmentSegment), lines 507 and 511

In line 551, the first character is actually cut off.

Again, this problem does not occur if one only worked with deployed models
in the Acceleo modules. Any reference to a locally deployed model is
problematic.

Is this a known issue? Shall I add a critical (I really think such
fundamental issue is critical to Acceleo) Bugzilla for this problem.

Best regards,
Marc-Florian


"Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...

Hi

This is the missing first letter problem. "Set(Parameter)" would have
been sensible.

Something somewhere has got a byte offset and it causes chaos. The
problem eventually goes away once you rebuild everything enough times.
I've not managed to work out where the inconsistency is.

Try cleaning, restarting, wiping the bin folders with your OS, switch
backwards and forwards between binary/ASCII emtl files, changing JRE to
some other version and back again, make sure your Kepler compiler
preferences are the same as on Indigo ...

Regards

Ed Willink


On 20/08/2013 15:29, Marc-Florian Wendland wrote:
> Dear all,
>
> I am migrating our software from Indigo to Kepler and I encountered the
> following error when trying to build the Acceleo project:
>
> Errors occurred during the build.
> Errors running builder 'Acceleo Builder' on project 'xxx'.
> The feature 'et(Parameter)' is not a valid feature
>
> As a result I do not have an output files generated.
>
> I cannot interpret this error message at all. Again, the very same project
> worked in Indigo.
>
> Thanks for any help in advance
> Marc-Florian
Re: [Acceleo] Problems with Builder in Kepler [message #1413371 is a reply to message #1413064] Thu, 28 August 2014 11:19 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Hi Ed,

no, it does not got away. It will only go away if the models are not located
in the local workspace. Did you encountered a different behavior?

Maybe someone from the Acceleo team could say a word about this?

Regards,
Marc-Florian

ps. Sorry for re-sending the mail over and over again. My client told me it
was not sent, so I retried.



"Ed Willink" wrote in message news:ltl4re$5nf$1@xxxxxxxxe.org...

Hi

Well-debugged.

A few users have encountered this.

It's certainly really irritating when it happens, but it does seem to go
away after enough rebuild/re-install cycles, so perhaps only major.

Absolutely worth a Bugzilla.

Regards

Ed Willink



On 27/08/2014 17:02, Marc-Florian Wendland wrote:
> Hi all,
>
> I eventually figured out the reason why the first character gets lost. It
> has nothing to do whatsoever with Acceleo compiler settings, encoding
> scheme, Eclipse or Java version or XMI parsing. The very reason for this
> is
> a technical deficiency of Acceleo to load/work with metamodels that are
> located in the workspace and not deployed in the Eclipse instance. After
> removing each and every reference to a locally available metamodel (I
> simply
> deployed the metamodels in my development environment) everything is fine
> with Acceleo.
>
> I debugged the location were the first character (in my case, instead of
> TestPlan Acceleo looked for estPlan) gets lost. It happens in this method:
>
> org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
>
> uriFragmentSegment), lines 507 and 511
>
> In line 551, the first character is actually cut off.
>
> Again, this problem does not occur if one only worked with deployed models
> in the Acceleo modules. Any reference to a locally deployed model is
> problematic.
>
> Is this a known issue? Shall I add a critical (I really think such
> fundamental issue is critical to Acceleo) Bugzilla for this problem.
>
> Best regards,
> Marc-Florian
>
>
> "Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...
>
> Hi
>
> This is the missing first letter problem. "Set(Parameter)" would have
> been sensible.
>
> Something somewhere has got a byte offset and it causes chaos. The
> problem eventually goes away once you rebuild everything enough times.
> I've not managed to work out where the inconsistency is.
>
> Try cleaning, restarting, wiping the bin folders with your OS, switch
> backwards and forwards between binary/ASCII emtl files, changing JRE to
> some other version and back again, make sure your Kepler compiler
> preferences are the same as on Indigo ...
>
> Regards
>
> Ed Willink
>
>
> On 20/08/2013 15:29, Marc-Florian Wendland wrote:
>> Dear all,
>>
>> I am migrating our software from Indigo to Kepler and I encountered the
>> following error when trying to build the Acceleo project:
>>
>> Errors occurred during the build.
>> Errors running builder 'Acceleo Builder' on project 'xxx'.
>> The feature 'et(Parameter)' is not a valid feature
>>
>> As a result I do not have an output files generated.
>>
>> I cannot interpret this error message at all. Again, the very same
>> project
>> worked in Indigo.
>>
>> Thanks for any help in advance
>> Marc-Florian
>
Re: [Acceleo] Problems with Builder in Kepler [message #1413420 is a reply to message #1413371] Thu, 28 August 2014 13:18 Go to previous message
Ed Willink is currently offline Ed Willink
Messages: 4110
Registered: July 2009
Senior Member
Hi

[You're not the first to be fooled into redundant resends.]

If it doesn't go away then it must be a critical issue. Before I
eliminated Acceleo from my daily tool set, I had a working rule that
org.eclipse.ocl.ecore must not be an open project to avoid Acceleo
getting confused in regard to development and run-time OCL models.

IMHO, and there is Bugzilla response in which Obeo agreed, the URI
resolution in Acceleo is deeply flawed. It uses heuristics to try to
make references created and saved within Eclipse load and resolve
standalone. This is a difficult challenge that needs careful design such
as OCL's ProjectMap class. For simple cases the heuristics make the
inadequate design work, for complex cases they make a bad situation worse.

Regards

Ed Willink

On 28/08/2014 12:19, Marc-Florian Wendland wrote:
> Hi Ed,
>
> no, it does not got away. It will only go away if the models are not
> located in the local workspace. Did you encountered a different behavior?
>
> Maybe someone from the Acceleo team could say a word about this?
>
> Regards,
> Marc-Florian
>
> ps. Sorry for re-sending the mail over and over again. My client told me
> it was not sent, so I retried.
>
>
>
> "Ed Willink" wrote in message news:ltl4re$5nf$1@xxxxxxxxe.org...
>
> Hi
>
> Well-debugged.
>
> A few users have encountered this.
>
> It's certainly really irritating when it happens, but it does seem to go
> away after enough rebuild/re-install cycles, so perhaps only major.
>
> Absolutely worth a Bugzilla.
>
> Regards
>
> Ed Willink
>
>
>
> On 27/08/2014 17:02, Marc-Florian Wendland wrote:
>> Hi all,
>>
>> I eventually figured out the reason why the first character gets lost. It
>> has nothing to do whatsoever with Acceleo compiler settings, encoding
>> scheme, Eclipse or Java version or XMI parsing. The very reason for
>> this is
>> a technical deficiency of Acceleo to load/work with metamodels that are
>> located in the workspace and not deployed in the Eclipse instance. After
>> removing each and every reference to a locally available metamodel (I
>> simply
>> deployed the metamodels in my development environment) everything is fine
>> with Acceleo.
>>
>> I debugged the location were the first character (in my case, instead of
>> TestPlan Acceleo looked for estPlan) gets lost. It happens in this
>> method:
>>
>> org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(String
>>
>>
>> uriFragmentSegment), lines 507 and 511
>>
>> In line 551, the first character is actually cut off.
>>
>> Again, this problem does not occur if one only worked with deployed
>> models
>> in the Acceleo modules. Any reference to a locally deployed model is
>> problematic.
>>
>> Is this a known issue? Shall I add a critical (I really think such
>> fundamental issue is critical to Acceleo) Bugzilla for this problem.
>>
>> Best regards,
>> Marc-Florian
>>
>>
>> "Ed Willink" wrote in message news:kv0472$u3i$1@xxxxxxxxe.org...
>>
>> Hi
>>
>> This is the missing first letter problem. "Set(Parameter)" would have
>> been sensible.
>>
>> Something somewhere has got a byte offset and it causes chaos. The
>> problem eventually goes away once you rebuild everything enough times.
>> I've not managed to work out where the inconsistency is.
>>
>> Try cleaning, restarting, wiping the bin folders with your OS, switch
>> backwards and forwards between binary/ASCII emtl files, changing JRE to
>> some other version and back again, make sure your Kepler compiler
>> preferences are the same as on Indigo ...
>>
>> Regards
>>
>> Ed Willink
>>
>>
>> On 20/08/2013 15:29, Marc-Florian Wendland wrote:
>>> Dear all,
>>>
>>> I am migrating our software from Indigo to Kepler and I encountered the
>>> following error when trying to build the Acceleo project:
>>>
>>> Errors occurred during the build.
>>> Errors running builder 'Acceleo Builder' on project 'xxx'.
>>> The feature 'et(Parameter)' is not a valid feature
>>>
>>> As a result I do not have an output files generated.
>>>
>>> I cannot interpret this error message at all. Again, the very same
>>> project
>>> worked in Indigo.
>>>
>>> Thanks for any help in advance
>>> Marc-Florian
>>
>
Previous Topic:[Acceleo] error in definition of Set
Next Topic:[Acceleo] Open source projects using acceleo?
Goto Forum:
  


Current Time: Fri Oct 31 06:33:03 GMT 2014

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

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