Some XSDs are missing after installing opennms-core
Description
I noticed that the XSDs located in opennms-config/src/main/resources/xsds (the ones that were converted from Castor to JAXB) does not exist in /opt/oennms/share/xsds after installing opennms-core.
Also something similar happen with jdbc-datacollection-config.xsd, which is associated with the project features/jdbc-collector/, deployed with opennms-core.
Fixed on revision 3421213fb14d9c27a36ac213cd965579830ba44b for 1.10
Alejandro Galue March 28, 2012 at 7:21 AM
The XSDs are being generated by a maven tool.
The problem is packaging. I mean after installing the RPM or DEB package, the XSDs are not there.
David Hustace March 28, 2012 at 12:42 AM
Edited
I was under the impression that we had a tool that was generating the XSDs for classes that have been moved away from Castor marshaling. This is very important issue. For example, tonight I wanted to investigate the XSD for datacollection-config to determine if there can be more than on <sysoid> or <sysoidmask> used for the same <systemDef> (systemDef should be system-def, btw, but we have a lot of that kinda those)
Alejandro Galue March 2, 2012 at 12:33 PM
Note: 1.10.0 contains jmx-datacollection-config.xsd because that has been refactored from castor after their release, but guess that current snapshots (1.10.1-SNAPSHOT) should experience something similar to the other XSDs.
I noticed that the XSDs located in opennms-config/src/main/resources/xsds (the ones that were converted from Castor to JAXB) does not exist in /opt/oennms/share/xsds after installing opennms-core.
These XSDs are:
datacollection-config.xsd
eventconf.xsd
jmx-datacollection-config.xsd
poll-outages.xsd
snmp-config.xsd
Also something similar happen with jdbc-datacollection-config.xsd, which is associated with the project features/jdbc-collector/, deployed with opennms-core.