Closed kehusa closed 9 years ago
skorsky
commented
9 years ago I got the same with tutorial 3.1 (3.Wrapping_ThingML_into_Kevoree\3.1_ThingML_Components_3_Kevoree_Deployments_java/timer.thingml) yesterday. I'm using ThingML version 0.6.0.201510091147 org.thingml.eclipse.feature.feature.group.
brice-morin
commented
9 years ago Can you test with version 0.6.0.201510122007?
Note that the "check for Updates" features of the HEADS IDE might be broken... if it does not work:
git clone https://github.com/SINTEF-9012/ThingML.gitand open the projectorg.thingml.eclipse.uiinto your current HEADS IDE and run this project as an Eclipse application, it will open another Eclipse, with the plugins updated. So that you can at least test if update is still failing.
kehusa
commented
9 years ago I have pulled from master and tried to run the plugin, but still the same result.
Knut Eilif
2015-10-13 9:22 GMT+02:00 Brice Morin notifications@github.com:
Can you test with version 0.6.0.201510122007?
Note that the "check for Updates" features of the HEADS IDE might be broken... if it does not work: git clone https://github.com/SINTEF-9012/ThingML.git and open the project org.thingml.eclipse.ui into your current HEADS IDE and run this project as an Eclipse application, it will open another Eclipse, with the plugins updated. So that you can at least test if update is still failing.
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-147627718 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
brice-morin
commented
9 years ago Well, I cannot reproduce the problem.........
skorsky
commented
9 years ago I've updated the thingml feature to the version you suggested. The stack overflow remains active. Java System Library is 1.8.0_60.
The error message starts with: Compiling with "Plain Java" (Platform: java) Selected input file: L/3.1_ThingML_Components_3_Kevoree_Deployments/_java/timer.thingml (C:\Users\mask\git\skorsky\training\3.Wrapping_ThingML_into_Kevoree\3.1_ThingML_Components_3_Kevoree_Deployments_java\timer.thingml) ERROR: Exeption calling ThingML Compiler: nullPlease contact the ThingML development teamjava.lang.StackOverflowError at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1081) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133)
kehusa
commented
9 years ago I guess then that we need to download a clean bundle to check. However, the download link: http://coreff5.istic.univ-rennes1.fr/jenkins/job/headside/ws/products.minimal/target/products/ does not work.
2015-10-13 9:35 GMT+02:00 Brice Morin notifications@github.com:
Well, I cannot reproduce the problem.........
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-147630725 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
brice-morin
commented
9 years ago @barais is the jenkins OK?
skorsky
commented
9 years ago Olivier told me on Friday to use http://headside.gforge.inria.fr/ to download the HEADS IDE.
brice-morin
commented
9 years ago @skorsky yes, but these links are updated manually (Olivier just did it this morning), so it is now always up to date
brice-morin
commented
9 years ago OK, now I could reproduce the error :-) I'll work on it and tell you when it is fixed. Maybe not today, most likely before the week end
brice-morin
commented
9 years ago Well... the latest HEADS IDE still does not use the latest ThingML plugins. It uses a version from 2015-10-03 instead of 2015-10-12...
brice-morin
commented
9 years ago The stack overflow seems solved now, but it is some strange parsing error, at least within Eclipse (seems to work in the ThingML standalone editor). However, when opening _javascript/FieldNode.thingml it produces the following warnings:
Parameter.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
VariableAssignment.property has multiplicity 1 but was resolved to multiple element
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
SendAction.port has multiplicity 1 but was resolved to multiple elements
SendAction.port has multiplicity 1 but was resolved to multiple elements
ReceiveMessage.port has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
VariableAssignment.property has multiplicity 1 but was resolved to multiple element
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
VariableAssignment.property has multiplicity 1 but was resolved to multiple element
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
Property.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Function.type has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
PropertyReference.property has multiplicity 1 but was resolved to multiple elements
Parameter.type has multiplicity 1 but was resolved to multiple elementsWe typically get some warnings, but so much warnings might indicate a problem with the parser....
kehusa
commented
9 years ago This is what it looks like in my editor: [image: Innebygd bilde 1] Strange, why only this file?
2015-10-13 21:27 GMT+02:00 Brice Morin notifications@github.com:
The stack overflow seems solved now, but it is some strange parsing error, at least within Eclipse (seems to work in the ThingML standalone editor). However, when opening _javascript/FieldNode.thingml it produces the following warnings:
Parameter.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements VariableAssignment.property has multiplicity 1 but was resolved to multiple element PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements SendAction.port has multiplicity 1 but was resolved to multiple elements SendAction.port has multiplicity 1 but was resolved to multiple elements ReceiveMessage.port has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements VariableAssignment.property has multiplicity 1 but was resolved to multiple element PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements VariableAssignment.property has multiplicity 1 but was resolved to multiple element PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements Property.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Function.type has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements PropertyReference.property has multiplicity 1 but was resolved to multiple elements Parameter.type has multiplicity 1 but was resolved to multiple elements
We typically get some warnings, but so much warnings might indicate a problem with the parser....
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-147823720 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
brice-morin
commented
9 years ago Cannot see the image... but I guess the four imports are red.
brice-morin
commented
9 years ago Also note that most files in the _javascript folder do not appear in the outline view, meaning they cannot really be parsed, meaning they cannot really be imported... Other files in the root (PIM) folder seem OK however
kehusa
commented
9 years ago Hmm, I hadn't seen the outline.
However, trying to generate code gives this error:
ERROR: The selected model contains errors: file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : The given URI contains a model with a wrong type file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : The given URI contains a model with a wrong type file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : The given URI contains a model with a wrong type file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : The given URI contains a model with a wrong type file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve thing SensorTimerJS file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve thing SensorJS file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve thing DecoderFilter file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve thing BLE file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve thing Decoder file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port timer file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port timer file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port decoder file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port decoder file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port filtered file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port filtered file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port BLEInternalRec file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port BLEInternal file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port BLE file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port BLE file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port decoder file:/C:/Users/KnutEilif/Heads_13.02/workspace/Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml : Cannot resolve port decoder Compilation stopped.
Is it anyway we can get the compilation to work even though the parser fails.
Knut Eilif
2015-10-14 9:52 GMT+02:00 Brice Morin notifications@github.com:
Also note that most files in the _javascript folder do not appear in the outline view, meaning they cannot really be parsed, meaning they cannot really be imported... Other files in the root (PIM) folder seem OK however
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-147965813 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
brice-morin
commented
9 years ago The compiler is likely to generate erroneous JS code if it cannot properly find things in the model. I am currently redoing your models in _javascript folder from scratch, copy/pasting block by block to see when the parser starts to fail.
kehusa
commented
9 years ago OK, strange stuff.
2015-10-14 10:34 GMT+02:00 Brice Morin notifications@github.com:
The compiler is likely to generate erroneous JS code if it cannot properly find things in the model. I am currently redoing your models in _javascript folder from scratch, copy/pasting block by block to see when the parser starts to fail.
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-147974307 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
brice-morin
commented
9 years ago To be precise, it is the parser integrated within Eclipse that goes wrong. The parser integrated in the standalone editor works, and compiler should work there as well.
kehusa
commented
9 years ago Do you think it is a possible to downgrade to the last working version while we search the bug? I am quite familiar with the HEADS IDE now and would very much like to continue working in that environment.
Knut Eilif
2015-10-14 15:16 GMT+02:00 Brice Morin notifications@github.com:
To be precise, it is the parser integrated within Eclipse that goes wrong. The parser integrated in the standalone editor works, and compiler should work there as well.
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-148046476 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
brice-morin
commented
9 years ago OK, I reverted to the version of September 29th. This one should work as I did a live demo at MODELS, and many participants successfully used it on different types of machines, though the thingml files were quite simple.
You should now be able to update your HEADS IDE as usual and get the old version of the ThingML plugin
brice-morin
commented
9 years ago Well... might need to reverse some more. Do you remember when you updated and when it did not work anymore?
kehusa
commented
9 years ago I think I updated last Saturday 10/10. My last generated files are from 8/10.
Knut Eilif
ons. 14. okt. 2015, 15:52 skrev Brice Morin notifications@github.com:
Well... might need to reverse some more. Do you remember when you updated and when it did not work anymore?
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-148056004 .
kehusa
commented
9 years ago This version is still not working for me at least. It must have been an earlier version.
2015-10-14 16:03 GMT+02:00 Knut Eilif Husa knut.eilif.husa@tellu.no:
I think I updated last Saturday 10/10. My last generated files are from 8/10.
Knut Eilif
ons. 14. okt. 2015, 15:52 skrev Brice Morin notifications@github.com:
Well... might need to reverse some more. Do you remember when you updated and when it did not work anymore?
— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/72#issuecomment-148056004 .
| Knut Eilif Husa | Tellu AS | Lensmannslia 4, 1386 Asker - NORWAY| Direct: +47 452 49496 | www.tellu.no |
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
When opening e.g. /Training/3.Wrapping_ThingML_into_Kevoree/3.3_Contrib/Tellu/Field-node/_javascript/FieldNode.thingml on github, the eclipse HEADS plugin causes a stack overflow: java.lang.StackOverflowError at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1081) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133) at org.sintef.thingml.impl.ReceiveMessageImpl.eSet(ReceiveMessageImpl.java:193) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1071) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1095) at org.sintef.thingml.impl.ThingMLElementImpl.eSet(ThingMLElementImpl.java:130) at org.sintef.thingml.impl.AnnotatedElementImpl.eSet(AnnotatedElementImpl.java:133)