For Comparable only two notices appears in section 4.2.2.:

• must be comparable
• Comparison methods for comparing two arbitrary amounts of the same currency, hereby comparing
  based on the (effective) numeric value (e.g. ignoring trailing zeroes).

When I run the TCK I get the following error report:

[FAILED]  4.2.2 For each amount class, test is Comparable.(ModellingMonetaryAmountsTest#testImplementComparable):
java.lang.AssertionError: Section 4.2.2: Comparable failed for: de.jfachwert.bank.Geldbetrag
	at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
	at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24)
	at org.javamoney.tck.tests.ModellingMonetaryAmountsTest.testImplementComparable(ModellingMonetaryAmountsTest.java:2522)
        ...

The input values for failed tests are:

• amount = "0 XXX"
• amount3 = "1 CHF"

The failing assert is assertTrue(amount.compareTo(amount3) > 0), or in other words

"0 XXX" > "1 CHF" should be true.

This is not covered by the specification (see above - or did I miss something?) and also from the semantic view I would expect it the other way around.

• Maven POM and settings.xml, see https://central.sonatype.org/pages/apache-maven.html
• Project Settings: Update CI_DEPLOY_PASSWORD for Sonatype/OSSH
• Dependencies to Test Audit Utils, they seem broken without Bintray, see jboss/jboss-test-audit#8

See JavaMoney/javamoney-parent#6

The POM still contains many references to java.net, e.g. issue tracker, mailing list, etc.

Migrated from https://java.net/jira/browse/JAVAMONEY-143

We had an earlier pointer to the Spec Lead (@atsticks) email address using java.net. That is outdated for sure, but now that we have 3 Maintenance Leads, should we use another address (e.g. a shared Gmail @atsticks and I maintained earlier) or all 3 or simply remove their mention?

Currently all pull request builds fail with

$ ~/bin/install-jdk.sh --target "/home/travis/oraclejdk7" --workspace "/home/travis/.cache/install-jdk" --feature "7" --license "BCL"
Ignoring license option: BCL -- using GPLv2+CE by default
install-jdk.sh 2019-07-17
Expected feature release number in range of 9 to 14, but got: 7
�[31;1mThe command "~/bin/install-jdk.sh --target "/home/travis/oraclejdk7" --workspace "/home/travis/.cache/install-jdk" --feature "7" --license "BCL"" failed and exited with 3 during .�

It looks as if oralcejdk7 is only available on precise builds. For trusty builds openjdk7 should be available.