For a couple weeks now the Nemo SonarQube analysis of the project has been failing with errors like this:
[ERROR] The project com.healthmarketscience.jackcess:jackcess:2.1.3-SNAPSHOT (/scratch/jenkins/workspace/ZZZZ_COBERTURA_jackess/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.healthmarketscience.jackcess:jackcess:2.1.3-SNAPSHOT: Could not find artifact com.healthmarketscience:openhms-parent:pom:1.1.3-SNAPSHOT in cloudbees-private-snapshot-repository (https://repository-sonarsource.forge.cloudbees.com/snapshot) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2]
I'm no Mavenista, so could someone point me in the right direction?
Thx,
Ann
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this is a result of some recent changes made to the parent pom (com.healthmarketscience:openhms-parent:pom:1.1.3-SNAPSHOT), and since that parent is not yet published anywhere, kaboom! You could probably work around this in the short term by locally building the openhms-parent project, and doing “mvn install” on that project. After doing so, you’ll have a local copy of the new parent pom, and downstream builds should be happier.
[ERROR] The project com.healthmarketscience.jackcess:jackcess:2.1.3-SNAPSHOT (/scratch/jenkins/workspace/ZZZZ_COBERTURA_jackess/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.healthmarketscience.jackcess:jackcess:2.1.3-SNAPSHOT: Could not find artifact com.healthmarketscience:openhms-parent:pom:1.1.3-SNAPSHOT in cloudbees-private-snapshot-repository (https://repository-sonarsource.forge.cloudbees.com/snapshot) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2]
I'm no Mavenista, so could someone point me in the right direction?
Hi,
For a couple weeks now the Nemo SonarQube analysis of the project has been failing with errors like this:
I'm no Mavenista, so could someone point me in the right direction?
Thx,
Ann
Hi Ann,
I think this is a result of some recent changes made to the parent pom (com.healthmarketscience:openhms-parent:pom:1.1.3-SNAPSHOT), and since that parent is not yet published anywhere, kaboom! You could probably work around this in the short term by locally building the openhms-parent project, and doing “mvn install” on that project. After doing so, you’ll have a local copy of the new parent pom, and downstream builds should be happier.
Dan
sorry, should be fixed now.