Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335760 - Spurious Possible incompatible type between ...
Summary: Spurious Possible incompatible type between ...
Status: CLOSED FIXED
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows Vista
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-29 07:20 EST by Ed Willink CLA
Modified: 2011-05-04 09:12 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2011-01-29 07:20:55 EST
3.1.0M4a

Just about every for loop reports a spurious warning such as

Possible incompatible type between 'Type' and 'OrderedSet(Type)'.
Comment 1 Laurent Goubet CLA 2011-01-29 13:54:18 EST
If I remember correctly, we've already fixed this since. Could you check with the latest promoted Nightly of the 3.1.0? (http://download.eclipse.org/modeling/m2t/acceleo/updates/nightly/3.1)
Comment 2 Ed Willink CLA 2011-02-02 13:36:33 EST
Problem persists in M5.
Comment 3 Ed Willink CLA 2011-02-02 13:38:52 EST
(Since in 336119 I have a problem with an unresolved proxy (EcorePackage), perhaps there's an unresolved proxy behind this problem too. Suggest explicit diagnostics for unresolved proxies.)
Comment 4 Stephane Begaudeau CLA 2011-02-09 08:39:24 EST
For me the problem has been fixed, and it should work since M5. I'll leave the bug open until you can confirm that everything works for you. I'll investigate this anyway in the case of a proxy for M6.
Comment 5 Ed Willink CLA 2011-03-15 16:19:47 EDT
Still a problem in M6.

For instance see CVS for

org.eclipse.mdt/org.eclipse.ocl/examples/org.eclipse.ocl.examples.build/src/org/eclipse/ocl/examples/build/acceleo/generateOclCommon.mtl
Comment 6 Stephane Begaudeau CLA 2011-03-19 10:46:05 EDT
I was working on a small generator at home and this problem re-appeared when I was working with a dynamic model. When I switched to a new Eclipse instance, the problem disappeared. I'll look into it Monday to see if it's really link to dynamic models. The comparison is done between an OCL expression and an "Acceleo variable declaration", maybe we have two versions of the same metamodel in memory, one in the OCL parser and one in the Acceleo parser.
Comment 7 Stephane Begaudeau CLA 2011-03-21 12:30:07 EDT
I have identified and fixed two problems with dynamic models. It is now working with all my examples, yet I'm pretty sure that there are still some problem with that algorithm. I'll have to test this more extensively tomorrow.