Brett, > Take a peek at: > http://maven.apache.org/maven-v3_0_0.xsd (Maven 1.1, can be used for > 1.0.2 as well) > http://maven.apache.org/maven-v4_0_0.xsd (Maven 2.0)
Looks good. :-) > And if you can tell me why properties in the first don't validate > <properties /> properly for the <war.bundle/> case, that'd be great :) Although you have specified that <properties/> can receive any XML elements, the "processContents" attribute is set to "lax". This means that contained elements will be validated if the validating XML parser has schema information for the namespace of elements inside the "any" section. In your example, <properties><war.bundle>...</war.bundle></properties> does not validate, because: a) war.bundle is not defined in Maven POM 4.0 namespace schema, and b) processContents is set to "lax" so that validation should be attempted for recognized namespaces that have schema information If processContents was set to "skip", the <war.bundle> would validate, but that seems very lenient. If "war" was defined as a namespace prefix, then: <properties><war:bundle>...</war:bundle></properties> would validate just fine. (Note. war-colon-bundle, not war-period-bundle). If you changed the style of property declaration to: <properties><property name="war.bundle">...</property></properties> that would also validate. Hope this helps, John Fallows. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
