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 21728 - Explorer doesn't display targets from included file (support <import>)
Summary: Explorer doesn't display targets from included file (support <import>)
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker with 2 votes (vote)
Assignee: Jesse Glick
: 25440 29883 41001 42069 43200 46631 (view as bug list)
Depends on: 42901
Blocks: 41535 44360
  Show dependency tree
Reported: 2002-03-19 19:16 UTC by Stefan Meisner Larsen
Modified: 2005-12-14 16:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Meisner Larsen 2002-03-19 19:16:45 UTC
If a xml file is included into build.xml using a http url, the targets
located in the include file isn't displayed in the explorer

The start of my build.xml file looks like this
<?xml version="1.0"?>

<!-- Define the entity buildsystem to point to buildsystem/common.xml -->
<!-- You may need to adjust the path of the buildsystem isn't checked out above
current directory -->
<!DOCTYPE project [ <!ENTITY buildsystem SYSTEM
""> ]>

<project name="perfmon" default="all" basedir=".">

    <!-- Define properties used by buildsystem -->
    <property name="project" value="${}"/>
    <property name="version" value="v100"/>
    <!-- This property holds a comma-seperated list of packagenames for -->
    <!-- which there should be generated javadoc -->
    <property name="packages.javadoc" value="dk.dannet.perfmon"/>
    <property name="build.compiler" value="modern"/>
    <!-- Include buildsystem/common.xml -->
Comment 1 Jesse Glick 2002-03-22 20:55:26 UTC
I don't see this being fixed anytime soon. The problem is that if you
show objects from included files, you have to decide what to do if
changes are made from the Explorer. Update the included file? Very
risky as it could be included from something else too. Make these
objects read-only? Perhaps, though somewhat strange UI.
Comment 2 David Konecny 2002-07-09 13:40:15 UTC
*** Issue 25440 has been marked as a duplicate of this issue. ***
Comment 3 Jesse Glick 2002-07-09 15:28:54 UTC
Not going to be fixed anytime soon. Perhaps when Ant module is
rewritten to use the XML support.
Comment 4 mgent 2002-07-10 19:24:09 UTC
I see the point about the difficulty in how to keep 
supporting the editing of ant build files if includes are 

However, what if you simply have a rule that says "if the 
ant file contains includes, it is considered readonly in 
the gui and will parse it properly"?

This could be combined with a switch in the IDE user 
options which allows the user to select what he/she 
prefers: the current non-fully-parsing but read/write 
behaviour, or the alternative readonly fully parsing 
behaviour (this choice being only excercised when there are 
includes present in the ant file.).

I doubt that any further clever features would ever be 
needed.  A full read/write fully-parsing infrastructure 
would be over the top IMHO.  I'd always have the option to 
edit the include file directly as text, which is fine by me.

People who use includes will either be able to edit the XML 
directly, or will have obtained the project from somewhere 
else and will therefore not want to modify the build file 
(unless you know what you're doing).
Comment 5 Jesse Glick 2002-07-10 19:38:54 UTC
I think it would suffice to make all files with entity includes r/o in
the Explorer and leave it at that (no option is really necessary).
Probably not so hard; not sure if it will make sense to implement it
or whether we will get real XML support soon anyway.
Comment 6 Jesse Glick 2003-01-08 21:14:05 UTC
*** Issue 29883 has been marked as a duplicate of this issue. ***
Comment 7 Jesse Glick 2003-12-19 15:46:48 UTC
For Ant 1.6 the same concern applies to <import>ed scripts. Might skip
support for DTD-based entity includes since these are essentially
obsoleted by the <import> directive.
Comment 8 Jesse Glick 2004-03-16 10:48:04 UTC
Should probably fix this for D at least for <import>.
Comment 9 Jesse Glick 2004-03-16 10:48:19 UTC
*** Issue 41001 has been marked as a duplicate of this issue. ***
Comment 10 Jesse Glick 2004-04-16 13:18:22 UTC
*** Issue 42069 has been marked as a duplicate of this issue. ***
Comment 11 Jesse Glick 2004-05-04 20:37:56 UTC
Waiting for issue #20532 is unrealistic.
Comment 12 Jesse Glick 2004-05-06 16:13:57 UTC
Could be useful for various project types, not just j2seproject.
Comment 13 Jesse Glick 2004-05-13 16:05:23 UTC
*** Issue 43200 has been marked as a duplicate of this issue. ***
Comment 14 Jesse Glick 2004-05-13 19:19:41 UTC
*** Issue 43200 has been marked as a duplicate of this issue. ***
Comment 15 Jesse Glick 2004-06-04 19:33:59 UTC
See commit info in issue #44360.
Comment 16 Jesse Glick 2004-07-27 19:55:57 UTC
*** Issue 46631 has been marked as a duplicate of this issue. ***
Comment 17 Marian Mirilovic 2005-12-14 16:01:34 UTC
verified in NB 5.0