[
https://issues.apache.org/jira/browse/MNG-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255307#comment-17255307
]
Michael Osipov commented on MNG-6830:
-------------------------------------
All of our POMs and Settings must be in the proper XML namespace otherwise the
file is logically empty.
POM: {{targetNamespace="http://maven.apache.org/POM/4.0.0"}}
Settings: {{targetNamespace="http://maven.apache.org/SETTINGS/1.1.0"}}.
Either via default namespace or an explicit namespace prefix.
> Warn on missing namespace
> -------------------------
>
> Key: MNG-6830
> URL: https://issues.apache.org/jira/browse/MNG-6830
> Project: Maven
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Minor
>
> We allow pom.xml files with no namespace and reject pom.xml files that use
> prefixed local names that are correctly namespaced.
> As step 1 to getting to a release where we can fix this, emit a warning when
> we encounter a non-namespaced pom.xml such as this:
> <project>
> <modelVersion>4.0.0</modelVersion>
> <packaging>war</packaging>
> <version>0.1.0-SNAPSHOT</version>
> <groupId>c.g</groupId>
> <artifactId>mvn25</artifactId>
> <properties>
> <appengine.maven.plugin.version>2.2.0</appengine.maven.plugin.version>
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
> <maven.compiler.source>1.8</maven.compiler.source>
> <maven.compiler.target>1.8</maven.compiler.target>
> <maven.compiler.showDeprecation>true</maven.compiler.showDeprecation>
> </properties>
> </project>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
