Timothy Reilly wrote: > Just an observation but when I attempt to add the maven 2 XSD's to > the XML Catalog within Eclipse I have issues with the key to use. > > This is due to the fact that both settings xsd and project xsd's > share the same target namespace. > The key may be Namespace Name or Schema Location - in both cases > these are the same.
Namespace is the same, but Location is not. However, the Location is only good for files which specify a schema location, which some may not. > Can the files be combined into pom.xsd? I don't > know xsd well enough to know if this can be avoided/restructure > somehow. I took a guess, and created a "central.xml" file, and pointed Eclipse at that (using Namespace as the key): <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified" targetNamespace="http://maven.apache.org/POM/4.0.0"; xmlns="http://maven.apache.org/POM/4.0.0";> <xs:include schemaLocation="assembly-1.1.0.xsd"/> <xs:include schemaLocation="component-1.1.0.xsd"/> <xs:include schemaLocation="lifecycle-mappings-1.0.0.xsd"/> <xs:include schemaLocation="maven-4.0.0.xsd"/> <xs:include schemaLocation="paramdoc-1.0.0.xsd"/> <xs:include schemaLocation="plugin-metadata-1.0.0.xsd"/> <xs:include schemaLocation="plugin-registry-1.0.0.xsd"/> <xs:include schemaLocation="profiles-1.0.0.xsd"/> <xs:include schemaLocation="repository-metadata-1.0.0.xsd"/> <xs:include schemaLocation="settings-1.0.0.xsd"/> </xs:schema> Eclipse then seemed happy providing appropriate content assist for both a pom and a settings file. I didn't test the myriad others. Max.
signature.asc
Description: OpenPGP digital signature
