Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Annex formatter sometimes throws IllegalStateException #2036

Closed
lwrage opened this issue Oct 25, 2019 · 0 comments · Fixed by #2037
Closed

Annex formatter sometimes throws IllegalStateException #2036

lwrage opened this issue Oct 25, 2019 · 0 comments · Fixed by #2037
Assignees
@lwrage
Labels
category:bug core importance:low
Milestone
2.6.0

Comments

@lwrage
Copy link
Contributor

@lwrage lwrage commented Oct 25, 2019 •
edited

To reproduce:

  1. Format an AADL file that has an EMV2 annex
  2. After that format an AADL file that has some annex X without a plugin for parsing X installed

There is a hack to store parse results. The last parse result from an Xtext parser is kept around even if we are processing an annex that is not xtext related. The last parse result must be cleared in these cases.
@lwrage lwrage self-assigned this Oct 25, 2019
@lwrage lwrage added this to the 2.6.0 milestone Oct 25, 2019
@lwrage lwrage mentioned this issue Oct 25, 2019
Merged
@joeseibel joeseibel changed the title Annex formatter sometines throws IllegalStateException Annex formatter sometimes throws IllegalStateException Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lwrage lwrage

Labels
category:bug core importance:low
Projects
None yet
Milestone
2.6.0
Development

Successfully merging a pull request may close this issue.

Clear AnnexParseUtil.lastparseresult before parsing an annex osate/osate2
1 participant
@lwrage