FHIR Chat · Build missing package cache? · IG creation

Stream: IG creation

Topic: Build missing package cache?

David Pyke (Mar 14 2019 at 12:59):

Missing package cache. I'm trying to rebuild my IG but I'm getting the following:
Fetch Package history from http://hl7.org/fhir/us/core-r4/package-list.json
Publishing Content Failed: http://hl7.org/fhir/us/core-r4/package-list.json?nocache=1552568226399 (35.0013sec)
(35.0013sec)
Use -? to get command line help (35.0013sec)
(35.0013sec)
Stack Dump (for debugging): (35.0013sec)
java.io.FileNotFoundException: http://hl7.org/fhir/us/core-r4/package-list.json?nocache=1552568226399
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1872)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at org.hl7.fhir.igtools.publisher.Publisher.fetchJson(Publisher.java:1656)
at org.hl7.fhir.igtools.publisher.Publisher.resolveDependency(Publisher.java:1640)
at org.hl7.fhir.igtools.publisher.Publisher.loadIg(Publisher.java:1561)
at org.hl7.fhir.igtools.publisher.Publisher.initializeFromJson(Publisher.java:1181)
at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:976)
at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:549)
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:5099)
Exception in thread "main" java.lang.NullPointerException
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:5109)

David Pyke (Mar 14 2019 at 13:00):

What am I doing wrong?

David Pyke (Mar 14 2019 at 13:00):

I'm dependent on uscore-r4 and it builds locally...

Eric Haas (Mar 14 2019 at 16:11):

in your ig.json your dependency should look something like...

David Pyke (Mar 14 2019 at 16:12):

<dependsOn>
<uri value="http://hl7.org/fhir/us/core-r4"/>
<packageId value="hl7.fhir.us.core.r4"/>
<version value="current"/>
</dependsOn>

Eric Haas (Mar 14 2019 at 16:12):

  "dependencyList": [
    {
      "name": "uscore",
      "location": "http://hl7.org/fhir/us/core-r4",
      "version": "current"
    }
  ],

David Pyke (Mar 14 2019 at 16:13):

Okay, I can change it to that

Eric Haas (Mar 14 2019 at 16:14):

I had qi core in there see the edits

David Pyke (Mar 14 2019 at 16:16):

IT has:
"dependencyList": [
{
"name" : "corer4",
"version" : "current",
"location" : "http://hl7.org/fhir/us/core-r4"}
],

David Pyke (Mar 14 2019 at 16:17):

I'm assuming that uscore-r4 is broken

Eric Haas (Mar 14 2019 at 16:17):

lets see...

David Pyke (Mar 14 2019 at 16:21):

Looks like it was rebuilt since. How can I force a new build to happen for mine?

David Pyke (Mar 14 2019 at 16:26):

Nope, rebuilding didn't fix it.

David Pyke (Mar 14 2019 at 16:27):

Do I need to repoint the dependency to build.fhir.org?

Eric Haas (Mar 14 2019 at 16:28):

its is not broken . and I am not getting that error. you can try manually loading the package in the .fhir folder

David Pyke (Mar 14 2019 at 16:28):

It builds locally, though. It only breaks here

David Pyke (Mar 14 2019 at 16:32):

I'm guessing that it's in my cache and works but it's not in http://hl7.org/fhir/us/core-r4/package-list.json

David Pyke (Mar 14 2019 at 16:32):

IS there a way to tell the build server to use a cached version? (assuming it's in the build server cache)?

Eric Haas (Mar 14 2019 at 16:33):

where is here?

David Pyke (Mar 14 2019 at 16:34):

build.fhir.org

David Pyke (Mar 14 2019 at 17:14):

Hmm, looks like it's not just me. Everything with a uscore-r4 dependency is breaking.

Grahame Grieve (Mar 14 2019 at 20:25):

dependency should be http://hl7.org/fhir/us/core

David Pyke (Mar 14 2019 at 21:19):

That breaks everything as that's the R3 USCore, not the R4 and I need the R4 for mine

David Pyke (Mar 14 2019 at 21:21):

Oh, wait, no, now I need to change all my profiles...

Grahame Grieve (Mar 14 2019 at 21:39):

specify the current version

David Pyke (Mar 14 2019 at 21:40):

Yep, I've fixed it, just trying to deal with a broken link that suddenly exists

John Moehrke (Mar 15 2019 at 14:20):

so, I am glad that fixed it... but the eLTSS IG really wants to specify R4 (or higher). By just using 'current' are we really saying R4? I don't think this is a strong concern, but a versionless linkage can be seen as endorsement of past versions (STU3, DSTU2)

Lloyd McKenzie (Mar 15 2019 at 14:53):

You can't have versionless references when content being referenced isn't normative. Once content is normative, we could explore the possibility of versionless dependendencies

Grahame Grieve (Mar 15 2019 at 19:05):

current is not versionless

Last updated: Apr 12 2022 at 19:14 UTC