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

Call Resolute via a proper API #1889

Closed
lwrage opened this issue Jul 11, 2019 · 4 comments
Closed

Call Resolute via a proper API #1889

lwrage opened this issue Jul 11, 2019 · 4 comments

Comments

@lwrage
Copy link
Contributor

lwrage commented Jul 11, 2019

We have code that allows calls to Resolute in org.osate.assure.util.ResoluteInterface.java. As it requires Resolute classes for compilation it should be moved to the resolute feature so it would be installed together with Resolute. If resolute is not installed the code is not executed in OSATE. Project org.osate.smaccm.stubs should be deleted.
There are a couple of other classes which depend on Resolute classes.

@reteprelief
Copy link
Contributor

Can you tell me where Collins is keeping SMACCM nowadays? Github tells me that the repository is archived.

@reteprelief
Copy link
Contributor

I found the new location

@lwrage lwrage added this to the 2.6.0 milestone Jul 12, 2019
@reteprelief reteprelief removed this from the 2.6.0 milestone Jul 24, 2019
@reteprelief reteprelief removed their assignment Nov 4, 2019
@lwrage lwrage changed the title Move code to call resolute to Resolute Call Resolute via a proper API Feb 12, 2021
@lwrage lwrage added this to the 2.10.0 milestone Feb 12, 2021
@jjhugues
Copy link
Contributor

As discussed with Lutz, we need to

  • Evaluate eventual compatibility issues with latest Resolute plugins
  • Provides a mechanism to register Resolute as an ALISA verification method instead of hardcoding it
  • Define a strategy to have this full capability restored

@lwrage lwrage removed this from the 2.10.0 milestone Jul 2, 2021
This was referenced May 27, 2022
@lwrage lwrage added this to the 2.12.0 milestone Feb 1, 2023
@lwrage
Copy link
Contributor Author

lwrage commented Mar 14, 2023

done

@lwrage lwrage closed this as completed Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants