What are the current design goals for the M2 pom xsd? The existing schema definition for Maven 1.x
http://maven.apache.org/xsd/maven-project-3.0.0.xsd has no namespace and uses sequence for child elements. Will Maven2 instance documents be required to specify a namespace in production? <project xmlns="http://maven.apache.org/xsd/maven-project-4.0.0.xsd"; > ... </project> This is useful for design time integration, rather than relying on just the filename. Is there a ordering requirement within pom.xml in practice? If not, it would seem appropriate to use <all> rather than <sequence> to define the child elements at each nested level within the document. This gives greater flexibility during editing, without sacrificing correctness. Kind Regards, John Fallows. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
