Stream: committers
Topic: Difficulties running publish on new installations
Khalid Shahin (Apr 28 2020 at 04:12):
Edit: I think I found the issue and I believe this effects all new committer and all new OS installations when it comes to building. Please see my proposed solutions to make to the master branch in my message below.
I have been running the FHIR publish process on my laptop since October 2018 and it works fine still. But I've tried to get it working on other Windows installations on a desktop and within VMs (everything is Windows 10), but I'm running into the same error on each of them. I've tried different versions of Java, Ant, Ruby, Jekyll but it's still coming up with the same error on each installation (other than my initial laptop install) when I try to run publish.bat. I'm wondering if I'm missing a step or if there's something that I could do to fix this problem. I attached the full log, but here's the final error messages.
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] :: UNRESOLVED DEPENDENCIES ::
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] :: ca.uhn.hapi.fhir#hapi-fhir-base;3.7.0-SNAPSHOT: not found
[ivy:resolve] :: org.fhir#ucum;1.0-SNAPSHOT: not found
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
"impossible to resolve dependencies:"
Jose Costa Teixeira (Apr 28 2020 at 04:23):
did you run the clean.bat?
Khalid Shahin (Apr 28 2020 at 13:45):
Jose Costa Teixeira said:
did you run the clean.bat?
These were fresh clones from the GitHub master branch. With that said I just ran clean.bat and then publish.bat and it's still the same exact problem.
Jason Walonoski (Apr 28 2020 at 16:54):
It is possible the 3.7.0-SNAPSHOT build is no longer available (that is quite old). It isn't a great long-term practice to rely on snapshots.
Khalid Shahin (Apr 28 2020 at 17:16):
Jason Walonoski said:
It is possible the
3.7.0-SNAPSHOTbuild is no longer available (that is quite old). It isn't a great long-term practice to rely on snapshots.
Does that mean ivy.xml will need to be changed? If so, should I make a Jira tracker item for this change to be made on the master branch? One way that I fixed it is I removed "-SNAPSHOT" from the HAPI and ucum lines in ivy.xml and it looks like it is working. But maybe they can remain as snapshot but be a newer version or some other change.
publish.bat still works on my original computer without any changes but maybe it's pulling the SNAPSHOTs from a cache. I see in my user folder there's ".ivy2" which has the needed snapshots. I copid this cache to my other installations and it fixed it. We will need to fix the FHIR build process because it won't work on new installations (at least for Windows).
Khalid Shahin (Apr 28 2020 at 17:32):
Problem: If you have a fresh Windows install (and possibly other OS as well) the FHIR build process won't be able to pull a couple of the needed dependencies. This is likely because the repos that it checks have removed the needed snapshots.
Proposed universal solutions (pick one):
- Committers will need to copy the two snapshots to their .ivy2 cache located in their user folder as part of the installation process. (Not practical, but it will work in the short term without any changes needed to the master branch)
- ivy.xml will need to be changed so it looks for different dependencies whether it's a newer version or with "-SNAPSHOT" removed from the couple lines.
- ivysettings.xml will include a repo that still has the removed snapshots.
- Other, if there's some other underlying issue.
I will make a Jira tracker item if one other person confirms this problem on a fresh OS install, and I'll include my three proposed solutions.
Vassil Peytchev (Apr 28 2020 at 17:40):
Confirmed by removing the .ivy2/cache/ca.uhn.hapi.fhir/ entry and running publish.sh. It is not OS-specific.
Khalid Shahin (Apr 28 2020 at 17:42):
Vassil Peytchev said:
Confirmed by removing the .ivy2/cache/ca.uhn.hapi.fhir/ entry and running publish.sh. It is no OS-specific.
Thank you. I'll make a Jira tracker item. Which of the proposed solutions do you think makes the most sense?
Vassil Peytchev (Apr 28 2020 at 17:44):
I think there is a general need to clean up the build process, so if there is no need for these dependencies, maybe they can be removed....
Khalid Shahin (Apr 28 2020 at 17:55):
Vassil Peytchev said:
I think there is a general need to clean up the build process, so if there is no need for these dependencies, maybe they can be removed....
Not sure about HAPI-3.7.0-SNAPSHOT, but ucum is needed for the build to continue.
Khalid Shahin (Apr 28 2020 at 20:48):
I made a Jira FHIR tracker item for this problem and with a few proposed solutions.
https://jira.hl7.org/browse/FHIR-26991
Grahame Grieve (Apr 29 2020 at 02:32):
this should be fixed now
Khalid Shahin (Apr 29 2020 at 11:03):
Grahame Grieve said:
this should be fixed now
That fixed the HAPI 3.7.0 snapshot issue, but there's still the missing dependency "org.fhir#ucum;1.0-SNAPSHOT" error.
Bryn Rhodes (Apr 29 2020 at 19:08):
I think this should be "org.fhir#ucum;1.0.2", base on the contents of the actual repository: https://repo1.maven.org/maven2/org/fhir/ucum/
Bryn Rhodes (Apr 29 2020 at 19:08):
I'm testing that change locally now
Grahame Grieve (Apr 29 2020 at 19:30):
https://github.com/HL7/fhir/pull/853 fixes this
Khalid Shahin (Apr 29 2020 at 20:42):
Tested it and it works. Thank you.
Last updated: Apr 12 2022 at 19:14 UTC
