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

Unify the way new versions of plugins are reference #21

Open
csnyulas opened this issue Oct 20, 2018 · 1 comment
Open

Unify the way new versions of plugins are reference #21

csnyulas opened this issue Oct 20, 2018 · 1 comment

Comments

@csnyulas
Copy link
Member

There is a mixture of ways latest versions of plug-ins are specified, and it is very confusing how the latest version is resolved. This is the case at least for the SNAP SPARQL and DL-Query plug-in, which have some versions included as part of the auto-update github project (see https://github.com/protegeproject/autoupdate/tree/master/snap-sparql-query and https://github.com/protegeproject/autoupdate/tree/master/dlquery), but different version of those plugins are referred from the plugins.repository file:
https://github.com/protegeproject/autoupdate/blob/master/plugins.repository

@csnyulas
Copy link
Member Author

Correction: this is the correct link to the plugins.repository for Protege version 5.x:

https://github.com/protegeproject/autoupdate/blob/master/update-info/5.0.0/plugins.repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant