"Morrison, John" wrote: > > No, I mean - should we specify that the <project> tag has to (or not) have a > name attribute?
I would lean to not mandating it. We can populate it to show by example it is available, but I don't think we should mandate its use. > > > -----Original Message----- > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > Sent: Monday, 01 October 2001 2:41 pm > > To: [EMAIL PROTECTED] > > Subject: Re: Build.xml standardization > > > > > > "Morrison, John" wrote: > > > > > > Ok, I'll change this back. Is the project name optional? > > > > Yes. The project name is to be managed internally to the build > > file. It is not something that the build process should really > > allow the user to override. > > > > Anyway, the ant project name is used for the "ant -projecthelp" > > calls. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > ======================================================================= > Information in this email and any attachments are confidential, and may > not be copied or used by anyone other than the addressee, nor disclosed > to any third party without our permission. There is no intention to > create any legally binding contract or other commitment through the use > of this email. > > Experian Limited (registration number 653331). > Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF > > --------------------------------------------------------------------- > 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]
