Closed Stachelbeck closed 11 years ago
Please make sure the project that contains the property set with the DurationType has a ProjectRefence to PluginResources.
Or do you get the error in the EMV2.aadl that is located in PluginResources? In that case can you do a clean build to see if it goes away?
Peter
From: Stachelbeck [mailto:notifications@github.com] Sent: Friday, February 01, 2013 1:59 PM To: osate/ErrorModelV2 Subject: [ErrorModelV2] Couldn't resolve reference property type 'Time_Range' in ErrorModelV2.development. (#1)
I have only one error left and it only occurs in Juno Eclipse with SR1 release. The error is in EMV2.aadl under org.sate.xtext.aadl2.errormodel. I do have XText v2.3.1 installed. The error is occuring on Time_Range. The lines are:
DurationType : type record ( TimeIntervale : Time_Range; Distribution : EMV2::DistributionFunction;);
The error message is:
Couldn't resolve reference to property type 'Time_Range'.Property set name may be missing.
Indigo Eclipse with SR2 release does not have this error.
Plus I do have a screen capture of Juno Eclipse show this error. I just do not know how to attach it to this issue.
Thanks,
— Reply to this email directly or view it on GitHubhttps://github.com/osate/ErrorModelV2/issues/1.
Peter,
Over the weekend I ran my procedures on my Red Hat Enterprise 6 MRG Linux box with a clean copy of Juno Eclipse release with SR1 and was able to download, compile, build and install with no errors from any of the modules in:
osate2-core
osate2-plugins
osate2-ErrorV2
I therefore, suspected I did not have a clean environment on my Windows 7 Desktop. So this Monday morning 2/4/2013 I deleted and recreated a clean Juno Eclipse release with SR1 on my Windows 7 Desktop and re-ran my procedures. This time I received no errors. So as of now I can no longer reproduce this problem.
Thanks for your time,
Kenneth Stachelbeck GTRI.
From: Peter Feiler [mailto:notifications@github.com] Sent: Friday, February 01, 2013 2:38 PM To: osate/ErrorModelV2 Cc: Stachelbeck, Kenneth Subject: Re: [ErrorModelV2] Couldn't resolve reference property type 'Time_Range' in ErrorModelV2.development. (#1)
Please make sure the project that contains the property set with the DurationType has a ProjectRefence to PluginResources.
Or do you get the error in the EMV2.aadl that is located in PluginResources? In that case can you do a clean build to see if it goes away?
Peter
From: Stachelbeck [mailto:notifications@github.com] Sent: Friday, February 01, 2013 1:59 PM To: osate/ErrorModelV2 Subject: [ErrorModelV2] Couldn't resolve reference property type 'Time_Range' in ErrorModelV2.development. (#1)
I have only one error left and it only occurs in Juno Eclipse with SR1 release. The error is in EMV2.aadl under org.sate.xtext.aadl2.errormodel. I do have XText v2.3.1 installed. The error is occuring on Time_Range. The lines are:
DurationType : type record ( TimeIntervale : Time_Range; Distribution : EMV2::DistributionFunction;);
The error message is:
Couldn't resolve reference to property type 'Time_Range'.Property set name may be missing.
Indigo Eclipse with SR2 release does not have this error.
Plus I do have a screen capture of Juno Eclipse show this error. I just do not know how to attach it to this issue.
Thanks,
— Reply to this email directly or view it on GitHubhttps://github.com/osate/ErrorModelV2/issues/1.
— Reply to this email directly or view it on GitHubhttps://github.com/osate/ErrorModelV2/issues/1#issuecomment-13010304.
I have only one error left and it only occurs in Juno Eclipse with SR1 release. The error is in EMV2.aadl under org.sate.xtext.aadl2.errormodel. I do have XText v2.3.1 installed. The error is occuring on Time_Range. The lines are:
DurationType : type record ( TimeIntervale : Time_Range; Distribution : EMV2::DistributionFunction;);
The error message is:
Couldn't resolve reference to property type 'Time_Range'.Property set name may be missing.
Indigo Eclipse with SR2 release does not have this error.
Plus I do have a screen capture of Juno Eclipse show this error. I just do not know how to attach it to this issue.
Thanks,