Hi Martin,
if he had implemented pom,xml his namespace declaration would either validate/not_validate xmlns as follows* While Maven itself ignores xmlns validation during its standard build process, IDEs (like IntelliJ or Eclipse) and external XML tools rely on xmlns and xsi:schemaLocation to provide code completion, syntax highlighting, and XML Schema Definition (XSD) validation. [1<https://maven.apache.org/plugins/maven-changes-plugin/using-changes-xsd.html>, 2<https://stackoverflow.com/questions/25996084/pom-xml-namespace-necessary>] * Explicit XML Validation: If you want Maven to actively validate XML files against a schema, you must use a plugin such as the XML Maven Plugin<https://www.mojohaus.org/xml-maven-plugin/validate-mojo.html> (org.codehaus.mojo:xml-maven-plugin). [1<https://www.mojohaus.org/xml-maven-plugin/validate-mojo.html>, 2<https://www.mojohaus.org/xml-maven-plugin/validation.html>] The implementation of xml_maven_plugin for validation would of course would need to happen within pom.xml and cannot be executed from settings.xml
You're talking of completely other things as Hans already mentioned in his mail.
Back to repository locations (which is important!) <!-- Define custom remote repositories --> <repositories> <repository> <id>my-custom-repo</id> <name>My Custom Repository</name> <url>https://myserver/repo</url> </repository> </repositories>
Also this was not my problem; see Tamás' mail. Regards Thorsten
OpenPGP_0x5A54BBB878225E08.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
