On 26/04/17 2:39 AM, Neil C Smith wrote:
On Fri, 17 Apr 2026 at 00:58, Michael Bien<[email protected]> wrote:
On 4/17/26 00:51, Ernie Rael wrote:
(NB error message misleading/not-useful)
yeah it is definitively of limited use without more details.
Well, strictly speaking, it's entirely accurate.
Now I see I should have said: accurate/misleading/not-useful. But at the
time... :)
The XML contains
invalid content because it contains an invalid namespace.
I guess, in the error dialog, "invalid xml content" refers to an xml
issue and not
what the pom's about. I may have read this as "invalid content in an xml
file".
The change
to https is not correct. It's a broken POM. Using Validate XML on
the POM will also fail, as will the Navigator, etc. The same issue
has been raised multiple times before, eg. in
https://github.com/apache/netbeans/pull/3012
Of course, it would be good if we were as lenient as the underlying
tools in cases like this, and at least offered to fix it.
Without an error/warning, I would prefer failure. You never know when you
might run into a strict tool.
As we move
to support Maven 4 it might be good to look at pushing more of this
work into Maven or Maveniverse tools (Toolbox, DomTrip, etc.)?
It might also be good if we could highlight the actual error when
opening the XML.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail:[email protected]
For additional commands, e-mail:[email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
