Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ant Wiki" for change notification.
The following page has been changed by SteveLoughran: http://wiki.apache.org/ant/Ant1%2e7%2e1/Planning The comment on the change is: Postponing some things until Ant1.7.2 ------------------------------------------------------------------------------ First, what is the goal? Bugs only, or bugs+features? + * Consensus is that Ant1.7.1 is bug fixes for regressions in Ant1.7.0 + == Goal == * Get all fixes since ant 1.7.0 into the hands of users * Refresh dependent libraries (xerces &c) - * Add some new features to keep everyone interested - == Release Plan == @@ -34, +34 @@ JanMatèrne: I'll set up a VMWare image of Vista Ultimate Edition (32bit, German) + * [ http://issues.apache.org/bugzilla/show_bug.cgi?id=41958 Javadocs breaking] === Would like to fix Defects === * Better proxy support on Java 5+ @@ -46, +47 @@ - when is ivy2.0.0 going to pass incubation? XavierHanin: Difficult to say, it depends on external factors. The major point for the moment is to recruit new committers. * modify fetch.xml to use Ivy. - * add support to <subant> a graph of targets, not just a list, so it can skip all dependents of a failing build - * any way to integrate download and declaration of an antlib? - === Scripting === * make <scriptcondition>, <scriptselector>, etc, more useful through : attributes and elements, re-use @@ -58, +56 @@ * should we include a scripting language? such as BSF+Rhino for a pre-java1.6 build? - need to vote on bundled language - I guess Rhino/JavaScript has mindshare right now - === Resource support === - * script tasks to load scripts from named resources - * import task to import from a given resource - * junit to select lists of tests to run from resources - - this may imply we need a way to get one resource to resolve a relative link to another resource...a new interface. - - === Testing === - - * implement something similar to <functionaltest> that steve uses in smartfrog for starting smartfrog and running tests against it. - * allow <waitfor> to fail if it times out (<functionaltest> will need this) - * enhancements to the XML reports format and stylesheets? TestNG and the CI tools folk may have input here. - * could we export a list of failing tests and use this as input for the next test run? to only run the tests that failed? - * could we use resources as a list of test classes to run, so drive off .class files in a JAR? === Java 1.6 enhancements === * Read filesystem properties in the packaging tasks. How to do this in a way that is x-platform and reliable? Add a new "useproperties" attribute to zip/zipfileset with "always", "never", "unix", and something on untar/unzip? * Selectors for selecting on system properties * chmod to switch to java API? Benefits? - * non-echo input handler for password entry + * non-echo input handler for password entry (done) === Big Project support === * BigProject logger with more logging of which project we are in (entry, exit, full location on an error), quiet on targets with no output, and in -verbose mode, log which build file a target actually came from. Maybe print finish time too. + - done but needs an XML version for use under Cruise Control. - * add a <antfork> task that runs a completely new ant process, with different env, maybe even JDK. Sometimes people need this; running forrest builds is just one example. We'd use <java> to set it up. === Internals === @@ -103, +87 @@ * produce our own RPMs. Which would imply we support them. * produce our own .deb (dpkg) as the Debian versions are always lagging and Ubuntu is becoming important in the Linux space and is based on Debian. - == Other enhancements == - * add an <xmlmessage> element for mail that takes an XML message, so you dont need to CDATA escape XHTML messages. == What to 'remove'/'trim' == * Which JDK are we now building on? (1.2, 1.3 or 1.4?) * When we know the build JDK, what code can we refactor/strip out? + + = Postponed For Ant 1.7.2 == + + === Other enhancements === + + * add an <xmlmessage> element for mail that takes an XML message, so you dont need to CDATA escape XHTML messages. + * add a <antfork> task that runs a completely new ant process, with different env, maybe even JDK. Sometimes people need this; running forrest builds is just one example. We'd use <java> to set it up. + * add support to <subant> a graph of targets, not just a list, so it can skip all dependents of a failing build + * any way to integrate download and declaration of an antlib? + + - == 'Antlibization' == + === 'Antlibization' === * Which optional tasks would be better as an antlib for separate download? + === Testing === + + * implement something similar to <functionaltest> that steve uses in smartfrog for starting smartfrog and running tests against it. + * allow <waitfor> to fail if it times out (<functionaltest> will need this) + * enhancements to the XML reports format and stylesheets? TestNG and the CI tools folk may have input here. + * could we export a list of failing tests and use this as input for the next test run? to only run the tests that failed? + * could we use resources as a list of test classes to run, so drive off .class files in a JAR? + + === Resource support === + + * script tasks to load scripts from named resources (done) + * import task to import from a given resource + * junit to select lists of tests to run from resources + + this may imply we need a way to get one resource to resolve a relative link to another resource...a new interface. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
