Problem with maven and repo

903 views
Skip to first unread message

Karl Fischer W.

unread,
Oct 30, 2020, 10:25:34 AM10/30/20
to HAPI FHIR
Hello Hapi folks !!
I'm deploying a new server right now, but there's a problem with the mvn stage

Step 3/11 : COPY pom.xml .
 ---> Using cache
 ---> c94301d34568
Step 4/11 : RUN mvn -ntp dependency:go-offline
 ---> Running in 7805fbdc248c
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for ca.uhn.hapi.fhir:hapi-fhir-jpaserver-starter:5.1.0: Could not transfer artifact ca.uhn.hapi.fhir:hapi-fhir:pom:5.1.0 from/to oss-snapshots (https://oss.sonatype.org/content/repositories/snapshots/): Transfer failed for https://oss.sonatype.org/content/repositories/snapshots/ca/uhn/hapi/fhir/hapi-fhir/5.1.0/hapi-fhir-5.1.0.pom and 'parent.relativePath' points at wrong local POM @ line 14, column 13
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project ca.uhn.hapi.fhir:hapi-fhir-jpaserver-starter:5.1.0 (/tmp/hapi-fhir-jpaserver-starter/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for ca.uhn.hapi.fhir:hapi-fhir-jpaserver-starter:5.1.0: Could not transfer artifact ca.uhn.hapi.fhir:hapi-fhir:pom:5.1.0 from/to oss-snapshots (https://oss.sonatype.org/content/repositories/snapshots/): Transfer failed for https://oss.sonatype.org/content/repositories/snapshots/ca/uhn/hapi/fhir/hapi-fhir/5.1.0/hapi-fhir-5.1.0.pom and 'parent.relativePath' points at wrong local POM @ line 14, column 13: Unknown host oss.sonatype.org: Temporary failure in name resolution -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:


It's safe to change to the new published version 5.2.0 ?

Thank you 

Karl Fischer

James Agnew

unread,
Oct 30, 2020, 10:28:41 AM10/30/20
to Karl Fischer W., HAPI FHIR
The error "Unknown host oss.sonatype.org: Temporary failure in name resolution" would suggest that your build machine is having network issues.

Cheers,
James

Verifique remitente, No abra adjuntos que no espera y no haga clic en vínculos. Ante cualquier duda comuníquese con la Gerencia de TI y Seguridad de la información (t...@sistemasexpertos.cl).  

Este correo es dirigido únicamente a las personas que aparecen como destinatarios y
puede contener información confidencial o privilegiada. Si usted recibió este correo
por error, por favor notificar inmediatamente al emisor y elimine el correo original.
Cualquier otro uso de este correo esta prohibido.

*********************************************************************************************

This message is for the designated recipient only and may contain privileged or
confidential information. If you have received it in error, please notify the sender
immediately and delete the original. Any other use of the email is prohibited.

--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hapi-fhir/624054f2-7a33-4725-a77e-cff10d8fffb9n%40googlegroups.com.

Karl Fischer W.

unread,
Oct 30, 2020, 10:43:31 AM10/30/20
to HAPI FHIR
Thank you James for your quick response.
It's weird because i see the repo and there's not v5.1.0
error (2).png
error2.png
Maybe a docker DNS resolution

James Agnew

unread,
Oct 30, 2020, 10:46:47 AM10/30/20
to Karl Fischer W., HAPI FHIR
Hmm, something weird is going with Maven there.. That isnt a SNAPSHOT version so it shouldn't be going to the snapshot repo.

Unfortunately, not really sure why... it doesn't do that in any of my environments. The release builds live here: https://repo1.maven.org/maven2/ca/uhn/hapi/fhir/

Message has been deleted
Message has been deleted

Karl Fischer W.

unread,
Oct 30, 2020, 1:47:55 PM10/30/20
to HAPI FHIR
Resolved, i figure out that was a internal DNS problem with Docker. With this command
sudo docker run busybox nslookup oss.sonatype.org
you can test if internal DNS resoltuion is working

Reply all
Reply to author
Forward
0 new messages