I had basically figured that out myself. Changing my build file is not what I want to do, and having to "un-filter" my targets to see them as normal is simply inconvenient. It was perfect before. I never use the menus anyway.
thanks, > Christian > > The ant builds in the ant pane are grey to indicate that they will be > hidden from the build, Ant menus. > If you want them to be visible, add a description attribute to the ant > target in the ant build.xml file, you can also select all targets in the > ant properties, Filter targets screen. > This behaviour allows hidden or inner targets in an ant build which you > may not want to invoke directly but would rather be invoked indirectly > through the use of a visible target. > > -- > Andrew Timberlake > Digital Design Development > http://www.ddd.co.za > mailto:[EMAIL PROTECTED] > 011 886 2299 > 082 415 8283 > > "If debugging is the process of removing bugs, > then programming must be the process of putting them in." > > On Sat, 2002-03-02 at 01:34, Christian Sell wrote: >> repeating myself, but anyway... >> >> What is the reason for the greying of ant build targets? I can see why the >> default target is bold - although it does not seem to fit the common >> practice of letting the default target only show a "usage" message. >> >> But why are all the other targets greyed out by default? I have many targets >> of equal importance (which is also a common and reasonable practice, just >> look at apache jakarta projects) and find I would have to go to the >> properties dialog and "un-filter" them manually to see them in standard >> black. >> >> Not as big an issue as the fat blue bar across my screen.. >> >> regards, >> Christian _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
