While working on the module,
@burke and I thought it is a good idea to release the working functionality and continue work on the rest functions.
While trying to release, I came across that maven release cannot happen when there are snapshot dependencies.
You can take a look at the module’s root pom here:
This file has been truncated.
<?xml version="1.0" encoding="UTF-8"?>
This Source Code Form is subject to the terms of the Mozilla Public License,
v. 2.0. If a copy of the MPL was not distributed with this file, You can
obtain one at http://mozilla.org/MPL/2.0/. OpenMRS is also distributed under
the terms of the Healthcare Disclaimer located at http://openmrs.org/license.
Copyright (C) OpenMRS Inc. OpenMRS is a registered trademark and the OpenMRS
graphic logo is a trademark of OpenMRS Inc.
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<name>Legacy UI Module</name>
Talking further with
@wyclif , there are a few questions that have come up.
Is a release required?
If yes, should look into some way of overcoming the snapshot dependencies.
I just see no value in making the effort to release a module that is never going to be used by anyone, there is no released platform version that requires the module since all released version, master and all our maintenance branches already have the legacy UI.
If you really want to release the module, I think you can set
-DignoreSnapshots=true so that the maven release plugin can ignore the snapshot dependency.