Reference Application Release 2.7 - Module Owners' / Maintainers Notification

Software Reference App
,
81

It’s strange, though, because it does appear to deploy the 1.10.6 distro jar (and I checked in the maven repo and it says it is there). An issue with resolving the maven repo after the move?

build	07-Nov-2017 18:52:27	[INFO] [INFO] Uploading: https://mavenrepo.openmrs.org/nexus/content/repositories/releases/org/openmrs/distro/platform/1.10.6/platform-1.10.6.jar
build	07-Nov-2017 18:52:27	[INFO] [INFO] Uploading: https://mavenrepo.openmrs.org/nexus/content/repositories/releases/org/openmrs/distro/platform/1.10.6/platform-1.10.6.pom
build	07-Nov-2017 18:52:27	[INFO] [INFO] ------------------------------------------------------------------------
build	07-Nov-2017 18:52:27	[INFO] [INFO] BUILD FAILURE
build	07-Nov-2017 18:52:27	[INFO] [INFO] ------------------------------------------------------------------------
build	07-Nov-2017 18:52:27	[INFO] [INFO] Total time: 9.313 s
build	07-Nov-2017 18:52:27	[INFO] [INFO] Finished at: 2017-11-07T18:52:27+00:00
build	07-Nov-2017 18:52:27	[INFO] [INFO] Final Memory: 28M/271M
build	07-Nov-2017 18:52:27	[INFO] [INFO] ------------------------------------------------------------------------
build	07-Nov-2017 18:52:27	[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project platform: Failed to deploy artifacts: Could not find artifact org.openmrs.distro:platform:jar:1.10.6 in openmrs-repo-releases (https://mavenrepo.openmrs.org/nexus/content/repositories/releases) -> [Help 1]
build	07-Nov-2017 18:52:27	[INFO] [ERROR]
82

@mogoodrich , in 699a812a4f3255de3301bdd3383f92a3b32904b0, you changed pom file from 1.10.5-SNAPSHOT to 1.10.6, a non-snapshot version.

So, the first job, as configured, uploaded all the artefacts. But, like any other maven build, it was expected to be an snapshot. Hence, task 3 of build #13 failed to release the very same artefacts you deployed on the task #1 of build #13. You should never commit by hand something as non-snapshot, leave that to the release plugin only.

You indeed reverted the commit in dcf2cf150f716caa3884358385c8e806a655a2d6, but the stable artefacts were already deployed to jfrog.

So it’s not really an issue, but it’s pretty much working as designed. The best solution is simply ignore 1.10.6 release, and change the pom file to 1.10.7-SNAPSHOT instead.

83

@cintiadr, thanks for chiming in. I will complete the 1.10.6 release manually by uploading the war and standalone to sourceforge.

@mogoodrich, I’ve updated the instructions to clarify on how to set the core version manually, if needed in the future.

84

Cool, thanks @cintiadr… I figured something like that happened. The issue was, I believe, that when the 1.10.5 version of core was released, a platform release wasn’t performed so I had to manually update the pom, but I should have updated it to 1.10.6-SNAPSHOT instead of 1.10.6.

Thanks @raff! Let me know if there’s anything else you need me to do.

Take care, Mark

85

I have added that here in the wiki.