[feature] add exist-db specific schema files to distribution output

[duncdrum]

Our tooling uses a number of exist specific xsd schema files, and we ship schemas for e.g. svg, Mondial, mathml, in exist/ect/webapp/WEB-INF/entities .

What's missing is schemas for exist-db specific files, like collection.xonf or repo.xml . So users who just modified or copied their conf.xml have no way to validate it from within the running instance, to check compatibility. Furthermore, as can be seen e.g. here eXide#784. Every time we change one of these schemas we need to a) copy the file into consuming packages, and avoid drift b) tie the consuming package to a single version of exist-db.

I want to suggest that we ship exist-db specific schemas as part of the distribution. We could also expose them via api, but at a minimum consuming packages should not require copies of exists native schemas, but locate and utilise the schemas that apply to a specific instance.

My likely incomplete list:

• repo.xml
• collection.xconf
• exist.xml(?)
• conf.xml

[duncdrum]

shout out to @adamretter from 2007 with exist 1.2 . The answer is: Yes it should

[adamretter]

@duncdrum all the missing schemas you are looking for should already be in the schemas/ folder where I created them