How right you are. Naturally, my naming of the test task conflicted with the Ant "test" task.
<sigh> Thanks for the patience. And mucho gratitude for fixing this in beta 3. ----- Original Message ----- From: "Diane Holt" <[EMAIL PROTECTED]> > --- "Hal Hildebrand (web)" <[EMAIL PROTECTED]> wrote: > > The issue is that I have build files that are designed to be called > > independently of one another, but also designed to be nested. > > But why is that still a problem with beta3? You won't get that message > (unless you're running -verbose), so long as you're not in fact trying to > define a task with the same name as a task that's already been defined but > associating it with a different class. IOW, if I run your example, but > change tasks.properties to define: > testit=test.TestTask > I never see any message about trying to override an old definition (unless > I run it -verbose -- which I think is probably actually wrong that it does > it even then, since I'm not re-defining the task, more just reiterating > its definition). > > Diane > > ===== > ([EMAIL PROTECTED]) > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
