> I'd like to kick off a discussion on what needs to be done to > get Ant 1.6 to a release.
New release +1 Ant 1.6 CVS version provides so many nice features that I vote for making a new release. In my opinion the official statement that JDK 1.2 is needed doesn´t mean that the whole tool has to be refactored. The change from 1.1 to 1.2 can take a longer time - but is in progress. > 4. xdocs proposal & manual generation > > I'm not sure if this is still at the proposal stage or ready for primetime. I > think we probably won't progress unless we agree that this is the way to > generate the Ant manual and commit to supporting it as part of the standard > build process. If it is the way to go, I'd like to hurry it along. > > Right now the setproxy doco is generated and looks a bit different from the > hand carved manual pages. We probably want a consistent look in the manual > and perhaps even a similar look to the rest of the Ant site. > Also I want to have some PDF generation going. +1 If the way how to generate NEW doco´s is specified, clear and tested, we can think about writing a tool for convert the old doco into the new format (or doing that by hand ...) But before fixing the process it makes no sence to spend time on conversion. > 5. lcp.bat replacement > > Yes, I have this in mind for a while and will get something > done soon on this > next. This will be necessary for Windows operation with the new jar > arrangement. On my windows machine I usually get errors because the classpath is longer than the environment variable can take ... and ANT_HOME is only c:/seu/ant16 ... (until now I have subst´ed that - and that works). > 6. New Tasks and new features. > > I've got some things I want to add to <parallel> to support timeouts, errors, > etc plus the capability to have daemon threads. I've thought about whether > <macrodef> could be done and would be a good idea. It would provide a way of > composing tasks into larger tasks. Peter has mentioned a system to provide > task default attribute settings for standard tasks. I've thought about an > <antschema> as a companion to <antstructure>, potentially supporting the > polymorphic stuff. Starting external programs that will continue after Ant is exiting will also be fine (often asked in mailing lists and jGuru). > 7. Bug reduction. > > I'd like to go through the bugs like a dose of salts. I'd like to see all > committers getting stuck into the backlog. The things that aren't going to be > done or are unlikely in the forseeable future (e.g. > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3807) could go, IMHO. > Voting for bugs will help us to prioritise them. Maybe we should do a "call for vote" on the [EMAIL PROTECTED] list and homepage? Jan
