Q: Running or debugging a model gives validation errors, but they are not shown in the editor.
A: If the editor reports no validation errors, but running or debugging the model reports errors, then there might be a problem with the line endings of the files. To solve this problem, save the file with windows line endings. This problem is often caused by Linux line endings.
Q: Why does the type system produce warnings instead of errors?
A: In POOSL models, the types of variables and parameters have no formal meaning; basically they are just pieces of documentation. When invoking a data method or operation, at simulation time the types of variables are determined. This means that it is impossible to perform a 100% correct type check while editing; therefore any data type related issues are reported while editing as warnings.
More information on this type checker can be found in the article "Static type checking without downcast operator".
Q: Why are some obvious suggestions missing in the content assist?
A: The content assist depends on the current context, which may be wrong if the model contains grammatical errors (such as a missing semi-colon ';'). Solve these errors before using the content assist.
Q: Why does a certain quick-fix have no effect?
A: Executing a quick-fix sometimes has no effect on the model. This can be caused by other errors that are still present in the model that are related to applied quick-fix. Solve these errors before executing the quick-fix.
Q: Why does "Help -> Check for Updates" not show any updates for Rotalumis?
A: Updates for Eclipse POOSL and Rotalumis plugins are released independently. To make sure that you are notified of Rotalumis updates, check that Rotalumis occurs in Help -> About Eclipse -> Installation Details -> Installed Software. If Rotalumis does not occur, please explicitly install Rotalumis (from the Eclipse POOSL update site); see the installation manual.
Q: What can I do about "OutOfMemoryError: Java heap space" or "GC overhead limit exceeded"?
A: The Eclipse installation folder contains a file eclipse.ini, which most likely contains a fragment like "-Xmx512m". This indicates that the maximum Java heap size is 512 megabyte. Increasing this amount (e.g., doubling it) should solve this problem.
Q: What can I do about "java.lang.StackOverflowError"?
A: The Eclipse installation folder contains a file eclipse.ini, which can be extended with a fragment like "-Xss4m". This indicates that the Java stack size is 4 megabyte. Adding this fragment, or increasing the amount (e.g., doubling it) should solve this problem.
Q: What can I do if the step buttons are disabled during a debug session?
A: Select a process or cluster in the Debug View. Or, reset the POOSL Debug perspective, by right-clicking in the top-right corner on the "POOSL Debug" perspective and selecting Reset.
Q: What can I do if the step buttons are invisible during a debug session?
A: Reset the POOSL Debug perspective, by right-clicking in the top-right corner on the "POOSL Debug" perspective and selecting Reset. Or, switch to the "POOSL Edit" perspective and afterwards back to the "POOSL Debug" perspective.
Q: What can I do about "Zero representations file found in "...". A modeling project must contain one."?
A: This means that the project has a modeling nature but does not contain an .aird file. The Modeling nature and .aird file are needed for graphical editing and are automatically added when opening a graphical editor.
There are 2 ways to fix this error:
Q: What is the file representations.aird, and how can I remove it?
A: The .aird file stores the graphical model information, and is automatically added when opening a graphical editor. To remove this file, first remove the Modeling nature from the project by right clicking the project in the Project Explorer -> Configure -> Remove Modeling Project Nature. If "Remove Modeling Project Nature" is not present, then the Modeling nature has already been removed.
Once the Modeling nature is removed, you can safely remove the representations.aird file: right click the representation.aird and select delete.
Q: What can I do about "The system cannot find the path specified" when trying to run or debug a model?
A: This can mean that Eclipse has restricted access in the Eclipse installation folder. To solve this issue, either run Eclipse as administrator (Right-click on eclipse.exe, select "Run as administrator"), or move the Eclipse installation folder to a location where it has full read and write access.`
Q: What can I do about a grey or red cross in the editor's sidebar or project explorer, when there is no error shown in the file (editor)?
A: This can happen when the validation mechanisms of Eclipse are out of sync. Forcing a new validation of the file can solve this issue.
This can be done by making a small adjustment (like adding a space) to the file and then save it. If this does not solve the problem, go to Project -> Clean -> select your project -> OK, which will force a validation of the whole project.
Q: What can I do about errors and warnings that seem not correct, or opening the declaration of an object (<F3>) navigates to the wrong object?
A: This can happen when the validation and linking mechanisms of Eclipse are out of sync.
Open the Project menu, and make sure that the option "Build Automatically" is activated (indicated by a checkmark in front of it). If it is not activated, click on "Build Automatically" to activate it.
Q: How can I run a POOSL model from the command line?
A: This is explained at https://www.es.ele.tue.nl/poosl/Tools/rotalumis/.
Q: Are there any known issues with Eclipse POOSL?
A: Please consult the issue tracker.
Q: Why do I have an 'incorrect' error on my import that shows that classes are already imported?
A: This can happen when importing the same file with a relative and an absolute path.
The model will see this as two different files which then import the same classes. To avoid the issue use the same format throughout the model.
Q: Why can't I use <F3> or <CTRL> + left-mouse-click in the textual editor to navigate to certain data classes or methods?
A: Navigation is not possible to files that do not exist in the project.
In particular this may happen when trying to navigate to data classes or methods from BasicClasses.poosl.
Q: Why can't I see the Poosl Include Paths in the Project Properties?
A:This can happen when the project is not configured as an Xtext project.
To add the Xtext configuration to the project, right click the project in the Project Explorer -> Configure -> Convert to Xtext Project.
The Poosl Include Paths should now be visible in the Project properties.