> >While this can be a powerful paradigm, it can also dillute the > effectiveness of > >Ant's original goal, "Ant is a Java based build tool.". > > Nope - the users don't care what the backend is - it could be > written in > perl or c and it wouldn't effect the users besides the few > who write tasks.
I agree that there could be confusion, but as long as you use names well, it's OK. Saying "Ant 2.0 is a flexible general-purpose blah blah, and by the way it can also do builds" will be very confusing. Much better is to say "Myrmidon is a flexible general-purpose blah blah. Ant 2.0 is a Java-based build tool, which by the way uses Myrmidon as its back-end." Alex
