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

OSATE plugin versions should change when its dependencies change #776

Closed
smithdtyler opened this issue Feb 8, 2017 · 3 comments
Closed

OSATE plugin versions should change when its dependencies change #776

smithdtyler opened this issue Feb 8, 2017 · 3 comments

Comments

@smithdtyler
Copy link

@smithdtyler smithdtyler commented Feb 8, 2017

As an author of plugins which depend on OSATE, it would be really helpful if minor/maintenance version numbers of OSATE builds were incremented when OSATE changes the versions of plugins it uses. This will allow me to better manage transitive dependencies.

For example, if I write a plugin that uses OSATE 2.2.1_xyz and xtext 1.0.0, then OSATE 2.2.1_xzw switches to xtext 2.0.0, I'm unable to constrain my OSATE dependency so that only OSATE versions using xtext 1.0.0 are used by my plugin. If OSATE instead increments from 2.2.1 to 2.2.2, I'm able to constrain my plugins appropriately.

If the top level version number (e.g., 2.2.1) is difficult to change due to its high visibility, I'd like a less visible version number I can rely on to manage transitive dependencies.

I have discussed this issue with @joeseibel
child of #1538

@lwrage
Copy link
Contributor

@lwrage lwrage commented Jan 14, 2020

As a first step we'll enable API analysis and Oomph version management such that we get errors if plugin versions must be changed.

@lwrage
Copy link
Contributor

@lwrage lwrage commented Jan 30, 2020

Requires some more experimentation with API tools and Oomph version management.

@lwrage lwrage added this to the 2.7.0 milestone Feb 3, 2020
@lwrage
Copy link
Contributor

@lwrage lwrage commented Feb 3, 2020

Closed in 5bb0b0d

@lwrage lwrage closed this as completed Feb 3, 2020
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

2 participants