Right, but are you considering this error behavior to be a bug? Because as far as I can see the pom.xml, despite OP's claims, is NOT valid.

This pom.xml uses xsi:schemaLocation="https://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd";.

The schema at https://maven.apache.org/xsd/maven-4.0.0.xsd declares xmlns="http://maven.apache.org/POM/4.0.0";.


On 4/10/20 12:30 PM, Emilian Bold wrote:
I suspect that's the problem: the URL itself is not resolved (because then it wouldn't have mattered if it's https vs http). So internally there *may* be a list of such schema URLs which expressly has the http URL and does nothing for the new https URL.

--emi


On Fri, Apr 10, 2020 at 7:29 PM Eric J. Schwarzenbach <eric.schwarzenb...@wrycan.com <mailto:eric.schwarzenb...@wrycan.com>> wrote:

    XML namespaces /look/ like urls by convention, but are not meant
    to actually be treated as urls and resolved. Is
    "https://maven.apache.org/POM/4.0.0";
    <https://maven.apache.org/POM/4.0.0> actually a valid namespace
    for the maven pom XML?

    On 4/10/20 1:39 AM, Emilian Bold wrote:
    Interesting. I think there's a whitelist of schema URLs in NetBeans
    and they have the original http variant. Please report this on JIRA,
    somebody might pick it up for 12 (which would be the next LTS
    version).

    --emi

    On Fri, Apr 10, 2020 at 3:25 AM Philip Durbin<philipdur...@gmail.com>  
<mailto:philipdur...@gmail.com>  wrote:
    I see what happened. In a recent pull request* we changed "http" to "https" 
in our pom.xml like this:

    BEFORE
    <project xmlns="http://maven.apache.org/POM/4.0.0";  
<http://maven.apache.org/POM/4.0.0>
    AFTER
    <project xmlns="https://maven.apache.org/POM/4.0.0";  
<https://maven.apache.org/POM/4.0.0>

    If I revert "https" back to "http" I can open the project properties.

    Phil

    *https://github.com/IQSS/dataverse/pull/6519



    On Thu, Apr 9, 2020 at 3:17 PM Philip Durbin<philipdur...@gmail.com>  
<mailto:philipdur...@gmail.com>  wrote:
    Hi, we are seeing the following error in Netbeans 11.3 and earlier versions 
such as Netbeans 8.2 even though our pom.xml is valid (I used xmllint to check 
it and others on my team used other validators):

    "Project's pom.xml contains invalid xml content. Please fix the file before 
proceeding."

    I'll also attach a screenshot.

    What I'm trying to do is right click the Java EE project and open the 
properties.

    Here's the commit I'm 
on:https://github.com/IQSS/dataverse/blob/d04d09c3e8d66295dc12e25f676a04a44b69acd6/pom.xml

    Any advice is welcome!

    Phil
    ---------------------------------------------------------------------
    To unsubscribe, e-mail:users-unsubscr...@netbeans.apache.org  
<mailto:users-unsubscr...@netbeans.apache.org>
    For additional commands, e-mail:users-h...@netbeans.apache.org  
<mailto:users-h...@netbeans.apache.org>

    For further information about the NetBeans mailing lists, visit:
    https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to