I like the second option as well. But then the concept of really hiding targets is gone, you can't base that on the presence or absence of a description attribute or can you?
A reaction to Conor: my intended use for the -targets flag is to supply a quick reminder to users of the build file. So I only want to include toplevel targets in the list. People who do maintenance on build.xml should open it up anyway, -targets is not for them. Regards, Marcel Schutte > -----Original Message----- > From: Siberski, Wolf [mailto:[EMAIL PROTECTED] > Sent: maandag 14 augustus 2000 15:36 > To: '[EMAIL PROTECTED]' > Subject: RE: [PATCH] Suggestion for new commandline switch -targets > > > If you want to mark targets as 'end-user' targets, > you should explicitly mark them. > Marking the tasks you don't want to show > is counter-intuitive and error-prone > (you may forget to mark a 'private' target, > or you may not update your existing build files). > > As a plus, with KC's approach you could > only publish targets by adding an explanation > to them. :-) > > What are the advantages of the 'private' flag? > > Wolf
