forked from srdc/cda2fhir
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix for jar #34
Closed
Closed
Fix for jar #34
Conversation
This file contains 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
…ncement' into UPMCFHIR-244-remove-text
…ncement' into UPMCFHIR-244-remove-text
…ncement' into UPMCFHIR-244-remove-text
…ystemName [UPMCFHIR-216] Changes for the OIDs, added Multum and NCI.
Upmcfhir 244 remove text
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
For no apparent reason, you have to do this when you run this as a .jar. Otherwise it doesn't work and frustrates you for hours. This thread sort of covers it.
srdc#4
Related JIRA tickets:
None.
How should this be manually tested?
Run through some files and see if anything seems amiss.
Background/Context:
Encountered this when trying to get the .jar to compile so it could run on their servers.
New JIRA tickets for clinical review required?