Uh oh!
There was an error while loading. Please reload this page.
Remove use of jboss repository that is so flaky - #142
Merged
Conversation
…ailable in labkey's Artifactory instance
bbimber
commented
May 24, 2022
Collaborator
If I want to use this on the discvr-22.3 branch, should this target that and merge this forward? |
labkey-jeckels
approved these changes
May 24, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
The jboss repository is nothing but trouble because it is quite unstable. We seem to need only one dependency from that repository (opencharts:opencharts:1.4.2), so this has been deployed to the ext-release-local repository in our Artifactory instance.
Related Pull Requests
Changes