From issues-return-157211-archive-asf-public=cust-asf.ponee.io@maven.apache.org Sun Dec 15 13:55:03 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 88B40180636 for ; Sun, 15 Dec 2019 14:55:03 +0100 (CET) Received: (qmail 38981 invoked by uid 500); 15 Dec 2019 13:55:02 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 38969 invoked by uid 99); 15 Dec 2019 13:55:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Dec 2019 13:55:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 778BFE3015 for ; Sun, 15 Dec 2019 13:55:01 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 38C34780459 for ; Sun, 15 Dec 2019 13:55:00 +0000 (UTC) Date: Sun, 15 Dec 2019 13:55:00 +0000 (UTC) From: "Elliotte Rusty Harold (Jira)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MNG-6036) Allow proper namespace usage for pom.xml MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MNG-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996732#comment-16996732 ] Elliotte Rusty Harold commented on MNG-6036: -------------------------------------------- This is a BFD. Not doing this right is a huge pain point for using the massive XML toolchain for processing Maven documents. I've seen it many times myself. It's just XSD but XSLT, XQuery, JDOM, XOM and every other XML tool for the last 20+ years. I'm totally on board for fixing this even if it causes massive breakage for existing poms that all have to fix their malformed XML. > Allow proper namespace usage for pom.xml > ---------------------------------------- > > Key: MNG-6036 > URL: https://issues.apache.org/jira/browse/MNG-6036 > Project: Maven > Issue Type: Bug > Components: core > Affects Versions: 3.3.9 > Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) > Maven home: /usr/local/Cellar/maven/3.3.9/libexec > Java version: 1.8.0_40, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.11.4", arch: "x86_64", family: "mac" > Reporter: Roland Huss > Priority: Major > > When I use the following pom.xml in order to allow an XSD for my custom plugin configuration: > {code:xml} > xmlns="http://maven.apache.org/POM/4.0.0" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/POM/4.0.0"> > .... > > .... > > ..... > > > .... > > {code} > I get this error: > {code} > [INFO] Scanning for projects... > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [ERROR] Malformed POM /Users/roland/Development/docker/docker-maven-plugin/samples/data-jolokia-demo/pom.xml: Unrecognised tag: 'm:configuration' (position: START_TAG seen ...che.org/POM/4.0.0" xmlns="http://fabric8.io/fabric8-maven-plugin">... @91:117) @ /Users/roland/Development/docker/docker-maven-plugin/samples/data-jolokia-demo/pom.xml, line 91, column 117 > @ > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project io.fabric8:docker-jolokia-demo:0.15-SNAPSHOT (/Users/roland/Development/docker/docker-maven-plugin/samples/data-jolokia-demo/pom.xml) has 1 error > [ERROR] Malformed POM /Users/roland/Development/docker/docker-maven-plugin/samples/data-jolokia-demo/pom.xml: Unrecognised tag: 'm:configuration' (position: START_TAG seen ...che.org/POM/4.0.0" xmlns="http://fabric8.io/fabric8-maven-plugin">... @91:117) @ /Users/roland/Development/docker/docker-maven-plugin/samples/data-jolokia-demo/pom.xml, line 91, column 117 -> [Help 2] > {code} > It would be awesome if the XML parser would resolve namespaces properly. Its not about adding namespace features, only for plain XML resolving (each decent XML these days should be able to do this transparently). > Except for https://cwiki.apache.org/confluence/display/MAVEN/Moving+forward+with+the+POM+data+model I couldn't find any statement when namespaces are supported or tolerated. Are there any plans for this (and maybe also to relax the schema constraints on the {{}} tag) ? > See also https://github.com/rhuss/poblano/issues/19 for a use case. -- This message was sent by Atlassian Jira (v8.3.4#803005)