Stream: implementers
Topic: latest version of the validator?
Hans van Amstel (Jul 10 2020 at 15:10):
Where can I download the latest version of the validator? Has this been changed recently?
When I look at https://github.com/hapifhir/org.hl7.fhir.core I see that the latest version is: 5.0.13-snapshot
https://fhir.github.io/latest-ig-publisher/ downloads 5.0.10
hl7 confluence points to [https://storage.googleapis.com/ig-build/org.hl7.fhir.validator.jar] which is version: 5.0.7-snapshot
John Moehrke (Jul 10 2020 at 15:11):
@Grahame Grieve
Vassil Peytchev (Jul 10 2020 at 15:44):
The latest ig-publisher is now at https://github.com/HL7/fhir-ig-publisher/releases/ - maybe worth checking out what validator version it will pull in?
New releases are announced in #tooling/releases
Mark Iantorno (Jul 10 2020 at 18:21):
(deleted)
Mark Iantorno (Jul 10 2020 at 18:21):
https://github.com/hapifhir/org.hl7.fhir.core/releases/latest/download/validator_cli.jar @Hans van Amstel
Mark Iantorno (Jul 10 2020 at 18:21):
:point_up: that link always points to the latest validator
Mark Iantorno (Jul 10 2020 at 18:23):
Test Cases, Validator, and IG-Publisher projects have now moved to a new release model, using GitHub release management
Mark Iantorno (Jul 10 2020 at 18:24):
Readmes for these projects have been updated accordingly to list the latest version and links to releases
Mark Iantorno (Jul 10 2020 at 18:25):
This website (https://fhir.github.io/latest-ig-publisher/) is no longer being updated.
Mark Iantorno (Jul 10 2020 at 18:26):
As Vassil mentioned, all relevant links will be posted in the automated release messages in tooling/releases channel. They were missing for the validator in that particular channel, but that has been fixed going forward.
Mark Iantorno (Jul 10 2020 at 18:26):
Please let me know if you have any questions.
Reece Adamson (Jul 13 2020 at 17:55):
@Mark Iantorno should this wiki page be updated to reflect the updated location? I just downloaded the latest from there and it gave me 5.0.7-SNAPSHOT and it looks like the GitHub release is more recent.
Mark Iantorno (Jul 13 2020 at 17:55):
Which wiki page?
Reece Adamson (Jul 13 2020 at 17:55):
sorry I forgot to link it!
https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator
Mark Iantorno (Jul 13 2020 at 17:56):
Yeah, I'd love to, but I have huge issues getting my account activated on the confluence system
Mark Iantorno (Jul 13 2020 at 17:56):
let me try again
Mark Iantorno (Jul 13 2020 at 17:57):
I just requested a password reset again, hopefully it works
Reece Adamson (Jul 13 2020 at 17:57):
I can change it if you'd like...I'm just not sure if there are any rules around who can make edits to the page
Mark Iantorno (Jul 13 2020 at 17:57):
That would be great, thanks
Reece Adamson (Jul 13 2020 at 18:13):
changed the link and renamed instances of org.hl7.fhir.validator.jar to validator_cli.jar to reflect the updated name of the downloaded jar.
Mark Iantorno (Jul 13 2020 at 18:25):
tyty
Reece Adamson (Jul 14 2020 at 20:10):
There are a few other sections of the validator documentation that I think may be out of date.
For example in the Loading an Implementation Guide
it says:
Alternatively, the -ig parameter can contain:
a URL that returns a relevant resource (profile, extension definition, code system or value set) to load
the name of a file that contains relevant resource to load, i.e. this can be a single profile file
the name of a directory that contains relevant resources (scan and load *.xml, *.json, and *.ttl - any that can be parsed)
based on a previous thread it's my understanding that pointing to a directory does not work, but that other acceptable methods include using the name of the package.tgz.
I mostly ask because we are using ValidationEngine directly (which points users to Confluence for acceptable inputs), but I'd be happy to update the docs while I'm at it if a maintainer can confirm the acceptable inputs.
Grahame Grieve (Jul 14 2020 at 20:34):
I think that's still correct. It certainly needs to be still correct
Grahame Grieve (Jul 14 2020 at 20:35):
it's the .pack file that is being deprecated
Reece Adamson (Jul 14 2020 at 21:22):
Thanks Grahame. Probably just a misunderstanding in the thread I mentioned where I believed pointing to a directory no longer worked. My directory was named definitions.json which I think may have caused confusion.
Reece Adamson (Jul 14 2020 at 21:23):
package.tgz isn't listed as an option in the docs currently, so I can add a bullet indicating that if you approve of the wording:
* the name of a gzipped tarball (e.g. package.tgz) that contains the relevant resources to load
Grahame Grieve (Jul 14 2020 at 23:13):
sure that would be a good addition
Last updated: Apr 12 2022 at 19:14 UTC
