Agreed, This should be done in ant 1.7.
Relying on dashes and descriptions for visiblity of targets is wrong. Peter On Friday 26 September 2003 09:43, Phil Weighill-Smith wrote: > We comment (with descriptions) all targets. Descriptions for targets > that are not public are there for build file maintenance. However, we > could always just remove descriptions and put them in as XML comments I > guess. But this conversation's really for a different forum now! > > Phil :n) > > On Thu, 2003-09-25 at 18:00, Steve Loughran wrote: > > Phil Weighill-Smith wrote: > > > This attribute would be rather handy for tools such as IntelliJ IDEA > > > which allows the graphical display of available targets for invocation > > > (within its Ant integration). It would be great if IDEA could know > > > which targets are "entry points" to the build file and only display > > > those for execution. For it to do this, the "public/private" attribute > > > would be needed. > > > > It does this. things without a description are shown as greyed > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
