[OpenNMS/opennms] 956dfd: NMS-19723: Fix stale trapd v1.1 XSD hash in change...
Scott Theleman via opennms-cvs <[email protected]>
| Newsgroups | gmane.network.opennms.cvs |
|---|---|
| Message-ID | <OpenNMS/opennms/push/refs/heads/jira/NMS-19723-trapd-mask-passwords/[email protected]> |
Branch: refs/heads/jira/NMS-19723-trapd-mask-passwords
Home: https://github.com/OpenNMS/opennms
Commit: 956dfdc93ea0cb4191a0b22b15d56c36378ab6bb
https://github.com/OpenNMS/opennms/commit/956dfdc93ea0cb4191a0b22b15d56c36378ab6bb
Author: Scott Theleman <[email protected]>
Date: 2026-07-22 (Wed, 22 Jul 2026)
Changed paths:
M features/config/upgrade/src/main/resources/changelog-cm/36.0.0/changelog-cm.xml
M features/config/upgrade/src/test/java/liquibase/ext2/cm/change/TrapdSchemaHashTest.java
Log Message:
-----------
NMS-19723: Fix stale trapd v1.1 XSD hash in changelog and tripwire test
The trapd-configuration-1.1.xsd shipped in commit 8636073abc8 hashes to
d5fdc5b9..., but both the changelog-cm.xml xsdFileHash and the
TrapdSchemaHashTest tripwire still carried ac286bc4..., a hash computed from an
earlier draft (before a trailing-whitespace cleanup on the schema). This failed
TrapdSchemaHashTest and, more importantly, would have failed the CM changelog
apply at startup, since importSchemaFromXsd validates the loaded XSD against the
declared hash. Update both to match the actual shipped schema. The changeSet is
new/unreleased on this branch, so no applied database is affected.
To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list
To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs