Gili created NETBEANS-250:
-----------------------------
Summary: Code-complete corrupts pom.xml when updating dependency
version
Key: NETBEANS-250
URL: https://issues.apache.org/jira/browse/NETBEANS-250
Project: NetBeans
Issue Type: Bug
Components: editor - Completion & Templates
Environment: Product Version: Apache NetBeans IDE Dev (Build
incubator-netbeans-release-163-on-20180105)
Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
Runtime: Java(TM) SE Runtime Environment 9.0.1+11
System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
Reporter: Gili
1. Open a pom.xml in a Maven project
2. Position the caret inside {{<version>}} of a dependency
3. Hit CTRL+SPACE to bring up code-complete
4. Select a different version number than what is currently set
5. If you were changing the version number from 1.6.0 to 1.6.1 then
code-complete will change the line from:
<version>1.6.0</version>
to:
<version>1.6.1</version>0</version>
Essentially, the portion of the version that needs to change gets left behind,
along with a trailing </version>
Expected behavior: Line should read "<version>1.6.1</version>"
This is a regression relative to version 8.2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
