[Acceleo] Problems with import [message #498950] |
Thu, 19 November 2009 10:14 |
Eclipse User |
|
|
|
Originally posted by: ilari.heikkinen.helsinki.fi
Hi,
I've been using Acceleo for roughly two weeks now and I've faced some
issues with the current version (0.9.0M3) import mechanism. Here's a
snippet from my project structure:
Application.mtl:
----------------
[module Application('http://myproject/ns/application')/]
[import DomainClass /]
[import Controller /]
[import View /]
[template public generateApplication(g : Application)]
[comment @main /]
[for (e : DomainClass | g.entities )]
[e.generate(g.packageName)/]
[/for]
[for (c : Controller | g.controllers )]
[c.generate(g.packageName)/]
[/for]
[for (v : View | g.views)]
[v.generate()/]
[/for]
[/template]
Controller.mtl:
---------------
[module Controller('http://myproject/ns/application')/]
[import Common /]
[template public generate(c : Controller, p : String)]
....
[/template]
The problem is that when I edit for example Controller and compile
(automatically), the routines are not resolved but marked as errors in
the editor. Now I have to do a clean for the project, "touch" the file
and compile the project again (via save). Errors are now disappeared but
are now existent in other files using the same Common library. I have to
do clean/touch/build -cycles for those modules also. Finally when all
modules using the Common library are clean of errors, the main
Application module cannot resolve the imported Domain/Controller/View
modules so I have to do a clean/touch/build -cycle for the main module also.
I'm using Eclipse 3.4.2 with EMF 2.4.2 and OCL 1.3. Running Eclipse on
Linux.
Do you guys see any error on my project structure or have ideas what
might cause these problems?
Thanks,
Ilari
--
Ilari Heikkinen
ilari.heikkinen@helsinki.fi
|
|
|
Re: [Acceleo] Problems with import [message #498993 is a reply to message #498950] |
Thu, 19 November 2009 13:30 |
|
This is a multi-part message in MIME format.
--------------060606090301090100040508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi Ilari,
We've observed and fixed a problem of the sort in the beginning of the
year, and never faced it again whatever the build we tested and whatever
the templates this build was tested on.
Could you raise a bugzilla describing the issue with your templates
attached so that we can try and fix the problem?
Laurent Goubet
Obeo
Ilari Heikkinen wrote:
> Hi,
>
> I've been using Acceleo for roughly two weeks now and I've faced some
> issues with the current version (0.9.0M3) import mechanism. Here's a
> snippet from my project structure:
>
> Application.mtl:
> ----------------
> [module Application('http://myproject/ns/application')/]
>
> [import DomainClass /]
> [import Controller /]
> [import View /]
>
> [template public generateApplication(g : Application)]
>
> [comment @main /]
> [for (e : DomainClass | g.entities )]
> [e.generate(g.packageName)/]
> [/for]
>
> [for (c : Controller | g.controllers )]
> [c.generate(g.packageName)/]
> [/for]
>
> [for (v : View | g.views)]
> [v.generate()/]
> [/for]
> [/template]
>
> Controller.mtl:
> ---------------
> [module Controller('http://myproject/ns/application')/]
>
> [import Common /]
>
> [template public generate(c : Controller, p : String)]
> ...
> [/template]
>
> The problem is that when I edit for example Controller and compile
> (automatically), the routines are not resolved but marked as errors in
> the editor. Now I have to do a clean for the project, "touch" the file
> and compile the project again (via save). Errors are now disappeared but
> are now existent in other files using the same Common library. I have to
> do clean/touch/build -cycles for those modules also. Finally when all
> modules using the Common library are clean of errors, the main
> Application module cannot resolve the imported Domain/Controller/View
> modules so I have to do a clean/touch/build -cycle for the main module
> also.
>
> I'm using Eclipse 3.4.2 with EMF 2.4.2 and OCL 1.3. Running Eclipse on
> Linux.
>
> Do you guys see any error on my project structure or have ideas what
> might cause these problems?
>
> Thanks,
> Ilari
>
--------------060606090301090100040508
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr">Obeo</a>
email;internet:laurent.goubet@obeo.fr
url:http://www.obeo.fr
version:2.1
end:vcard
--------------060606090301090100040508--
|
|
|
Re: [Acceleo] Problems with import [message #499025 is a reply to message #498993] |
Thu, 19 November 2009 14:57 |
Eclipse User |
|
|
|
Originally posted by: ilari.heikkinen.helsinki.fi
Hi,
filed a new bugzilla entry:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=295598
I want to emphasize that this happens specifically on Linux platform and
I recall not seeing this on Windows (unconfirmed though).
Best regards,
Ilari
On 19/11/09 15:30, Laurent Goubet wrote:
> Hi Ilari,
>
> We've observed and fixed a problem of the sort in the beginning of the
> year, and never faced it again whatever the build we tested and whatever
> the templates this build was tested on.
>
> Could you raise a bugzilla describing the issue with your templates
> attached so that we can try and fix the problem?
>
> Laurent Goubet
> Obeo
>
> Ilari Heikkinen wrote:
>> Hi,
>>
>> I've been using Acceleo for roughly two weeks now and I've faced some
>> issues with the current version (0.9.0M3) import mechanism. Here's a
>> snippet from my project structure:
>>
>> Application.mtl:
>> ----------------
>> [module Application('http://myproject/ns/application')/]
>>
>> [import DomainClass /]
>> [import Controller /]
>> [import View /]
>>
>> [template public generateApplication(g : Application)]
>> [comment @main /]
>> [for (e : DomainClass | g.entities )]
>> [e.generate(g.packageName)/]
>> [/for]
>>
>> [for (c : Controller | g.controllers )]
>> [c.generate(g.packageName)/]
>> [/for]
>>
>> [for (v : View | g.views)]
>> [v.generate()/]
>> [/for]
>> [/template]
>>
>> Controller.mtl:
>> ---------------
>> [module Controller('http://myproject/ns/application')/]
>>
>> [import Common /]
>>
>> [template public generate(c : Controller, p : String)]
>> ...
>> [/template]
>>
>> The problem is that when I edit for example Controller and compile
>> (automatically), the routines are not resolved but marked as errors in
>> the editor. Now I have to do a clean for the project, "touch" the file
>> and compile the project again (via save). Errors are now disappeared
>> but are now existent in other files using the same Common library. I
>> have to do clean/touch/build -cycles for those modules also. Finally
>> when all modules using the Common library are clean of errors, the
>> main Application module cannot resolve the imported
>> Domain/Controller/View modules so I have to do a clean/touch/build
>> -cycle for the main module also.
>>
>> I'm using Eclipse 3.4.2 with EMF 2.4.2 and OCL 1.3. Running Eclipse on
>> Linux.
>>
>> Do you guys see any error on my project structure or have ideas what
>> might cause these problems?
>>
>> Thanks,
>> Ilari
|
|
|
Re: [Acceleo] Problems with import [message #499032 is a reply to message #499025] |
Thu, 19 November 2009 15:36 |
|
This is a multi-part message in MIME format.
--------------040107070601050301020003
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Ilari,
I use Acceleo on Linux myself and haven't observed this bug since the
beginning of 2009. Thanks for the bug, we'll try and reproduce this on
the latests builds.
Laurent Goubet
Obeo
Ilari Heikkinen wrote:
> Hi,
>
> filed a new bugzilla entry:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=295598
>
> I want to emphasize that this happens specifically on Linux platform and
> I recall not seeing this on Windows (unconfirmed though).
>
> Best regards,
> Ilari
>
> On 19/11/09 15:30, Laurent Goubet wrote:
>> Hi Ilari,
>>
>> We've observed and fixed a problem of the sort in the beginning of the
>> year, and never faced it again whatever the build we tested and whatever
>> the templates this build was tested on.
>>
>> Could you raise a bugzilla describing the issue with your templates
>> attached so that we can try and fix the problem?
>>
>> Laurent Goubet
>> Obeo
>>
>> Ilari Heikkinen wrote:
>>> Hi,
>>>
>>> I've been using Acceleo for roughly two weeks now and I've faced some
>>> issues with the current version (0.9.0M3) import mechanism. Here's a
>>> snippet from my project structure:
>>>
>>> Application.mtl:
>>> ----------------
>>> [module Application('http://myproject/ns/application')/]
>>>
>>> [import DomainClass /]
>>> [import Controller /]
>>> [import View /]
>>>
>>> [template public generateApplication(g : Application)]
>>> [comment @main /]
>>> [for (e : DomainClass | g.entities )]
>>> [e.generate(g.packageName)/]
>>> [/for]
>>>
>>> [for (c : Controller | g.controllers )]
>>> [c.generate(g.packageName)/]
>>> [/for]
>>>
>>> [for (v : View | g.views)]
>>> [v.generate()/]
>>> [/for]
>>> [/template]
>>>
>>> Controller.mtl:
>>> ---------------
>>> [module Controller('http://myproject/ns/application')/]
>>>
>>> [import Common /]
>>>
>>> [template public generate(c : Controller, p : String)]
>>> ...
>>> [/template]
>>>
>>> The problem is that when I edit for example Controller and compile
>>> (automatically), the routines are not resolved but marked as errors in
>>> the editor. Now I have to do a clean for the project, "touch" the file
>>> and compile the project again (via save). Errors are now disappeared
>>> but are now existent in other files using the same Common library. I
>>> have to do clean/touch/build -cycles for those modules also. Finally
>>> when all modules using the Common library are clean of errors, the
>>> main Application module cannot resolve the imported
>>> Domain/Controller/View modules so I have to do a clean/touch/build
>>> -cycle for the main module also.
>>>
>>> I'm using Eclipse 3.4.2 with EMF 2.4.2 and OCL 1.3. Running Eclipse on
>>> Linux.
>>>
>>> Do you guys see any error on my project structure or have ideas what
>>> might cause these problems?
>>>
>>> Thanks,
>>> Ilari
>
>
--------------040107070601050301020003
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr">Obeo</a>
email;internet:laurent.goubet@obeo.fr
url:http://www.obeo.fr
version:2.1
end:vcard
--------------040107070601050301020003--
|
|
|
Powered by
FUDForum. Page generated in 0.04288 seconds