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

Warn about conflicts between update sites #36

Open
hinerm opened this issue Mar 26, 2015 · 2 comments
Open

Warn about conflicts between update sites #36

hinerm opened this issue Mar 26, 2015 · 2 comments

Comments

@hinerm
Copy link
Member

hinerm commented Mar 26, 2015

When update sites ship modified versions of the same jar, it would be nice if we could issue some sort of warning about potential incompatibility/conflicts.

@hinerm hinerm added this to the unscheduled milestone Mar 26, 2015
@ctrueden
Copy link
Member

It's tricky without special-casing certain update sites. In particular, many update sites override some files from the Fiji site, and this is just fine. The issue is when there are two "third party" update sites that both override the same file—then it becomes less clear which one should "win", or really if either one taking precedence will result in a mutually compatible state.

@hinerm
Copy link
Member Author

hinerm commented Mar 26, 2015

@ctrueden agreed. Sorry, I meant "non-core update sites" in the original description. And because of that ambiguity I propose just issuing warnings about the potential for problems, instead of trying to actually determine if state is compatible.

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