This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 97384 - Don't close already closed tags
Summary: Don't close already closed tags
Status: RESOLVED WONTFIX
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P4 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-07 14:19 UTC by pzajac
Modified: 2009-12-21 05:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2007-03-07 14:19:25 UTC 
20070305

I was editing ant build scriph"

Example:
    <target name="coverage-runtests">
        <antcall target="runtests">
            <param name="coverage.lib.path" location="${emma.dir}/emma.jar"/>
            <param name="xtest.jvm.coverage.args"
value="-Demma.coverage.out.file=${coverage.dir}/coverage.emma"/>
            <param name="xtest.ide.coverage.args"
value="-J-Dnetbeans.security.nocheck=true
-J-Demma.coverage.out.file=${coverage.dir}/coverage.emma"/>
        </antcall>
    </target>
--
The target
        <antcall target="runtests">
is already closed.

Code completion at:
<antcall target="runtests">xx

closes the tag
Comment 1 Samaresh Panda 2007-09-26 23:30:55 UTC 
This is going to be expensive.
Comment 2 pzajac 2007-09-27 08:34:17 UTC 
Expensive doesn't mean enhancement.
Comment 3 Samaresh Panda 2007-10-01 03:22:26 UTC 
It'll be nice to have, but not important at this point on the priority list.
Comment 4 Quality Engineering 2009-12-21 05:43:27 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team