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.

Sign up for GitHub

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

API Analysis builder reports bogus API changes #2204

Closed
lwrage opened this issue Feb 14, 2020 · 1 comment
Closed

API Analysis builder reports bogus API changes #2204

lwrage opened this issue Feb 14, 2020 · 1 comment
Assignees
@lwrage
Labels
category:releng
Milestone
2.7.1

Comments

@lwrage
Copy link
Contributor

lwrage commented Feb 14, 2020 •
edited
Loading

Summary

Sometimes the API analysis tools report invalid errors on code generated from xtend.

Expected and Current Behavior

Errors should only be reported if they are real errors.

Steps to Reproduce

Perform a clean build.

Environment

  • OSATE Version: 2.7.1-SANPSHOT
  • Operating System:
@lwrage lwrage added this to the 2.7.1 milestone Feb 14, 2020
@lwrage lwrage self-assigned this Feb 14, 2020
@lwrage lwrage changed the title API Analysis builder reports bogous API changes API Analysis builder reports bogus API changes Mar 2, 2020
@lwrage
Copy link
Contributor Author

lwrage commented Mar 2, 2020

The API analysis builder doesn't work well with the xtend builder. Workaround: avoid clean build whenever possible.

Instructions how to get rid of bogus errors are at https://github.com/osate/osate2/wiki/Managing-Feature-and-Plugin-Versions#errors-in-java-code-generated-from-xtend-after-a-clean-build

@lwrage lwrage closed this as completed Mar 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lwrage lwrage

Labels
category:releng
Projects
None yet
Milestone
2.7.1
Development

No branches or pull requests
1 participant
@lwrage