[BLUEJ-495] BlueJ parser rejects extra semi-colons at top-level of compilation unit
The BlueJ parser rejects extra semi-colons at the top-level of a compilation unit. For instance, an extra semi-colon after a package statement, import statement or class/interface/enum definition causes the "unparse-able" marker to appear on the class in the class diagram.
Issue metadata
- Issue type: Bug
- Priority: Low
- Fix versions: 3.1.1