there's a small window where we pick the latest f-m-p version and its not yet sync'd to maven central #172

jstrachan · 2016-10-01T17:14:17Z

just ran a CD pipeline while waiting for the sync to happen on 3.1.62; the pipeline decided 3.1.62 was the latest version of f-m-p but there was no pom or jar!

We maybe need to double check we can download it first and if not try the previous etc

jstrachan · 2016-10-10T11:59:52Z

moving to just 'mvn install" should do the trick now

abouchama · 2016-10-10T12:13:31Z

By deleting nexus pod:

oc delete pods nexus-1-29a4j

The error disappear:

[ERROR] Plugin io.fabric8:fabric8-maven-plugin:3.1.68 or one of its dependencies could not be resolved: Could not find artifact io.fabric8:fabric8-maven-plugin:jar:3.1.68 in nexus (http://nexus/content/groups/public) -> [Help 1]

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

there's a small window where we pick the latest f-m-p version and its not yet sync'd to maven central #172

there's a small window where we pick the latest f-m-p version and its not yet sync'd to maven central #172

jstrachan commented Oct 1, 2016

jstrachan commented Oct 10, 2016

abouchama commented Oct 10, 2016 •

edited

Loading

there's a small window where we pick the latest f-m-p version and its not yet sync'd to maven central #172

there's a small window where we pick the latest f-m-p version and its not yet sync'd to maven central #172

Comments

jstrachan commented Oct 1, 2016

jstrachan commented Oct 10, 2016

abouchama commented Oct 10, 2016 • edited Loading

abouchama commented Oct 10, 2016 •

edited

Loading