You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.

antnews.xml 3.8 kB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. <?xml version="1.0"?>
  2. <document>
  3. <properties>
  4. <author email="conor@cortexebusiness.com.au">Conor MacNeill</author>
  5. <author email="stefan.bodewig@epost.de">Stefan Bodewig</author>
  6. <title>Ant News</title>
  7. </properties>
  8. <body>
  9. <section name="Vote for a Logo">
  10. <h3>Polls have closed</h3>
  11. <p>
  12. Thanks for voting!
  13. </p>
  14. <p>*drum roll* - <a href="logocontest.html">and the winners are....</a></p>
  15. </section>
  16. <section name="Ant 1.4.1">
  17. <h3>11 October 2001 Ant 1.4.1 released !</h3>
  18. <p>Please visit the
  19. <a href="http://www.apache.org/dist/jakarta/jakarta-ant/release/v1.4.1/">
  20. download area</a>.
  21. </p>
  22. </section>
  23. <section name="Ant 2.0 Requirements Collected - Next is Design">
  24. <p>A commented version of the collected user requirements is now
  25. available <a href="ant2/features.html">here</a> - it is not
  26. complete as some details still have to be defined, but it should
  27. give you an idea of what Ant2 is going to look like.</p>
  28. <p>Several details can only be decided in the light of real code
  29. and prototypes. Several people are working on prototypes (that
  30. can be found in Ant's CVS module in the proposals directory) and
  31. discussion is going on on the Ant-Dev mailing list.</p>
  32. </section>
  33. <section name="Best-Practices Profile of Ant at Sun&apos;s Dot-Com Builder">
  34. <p>Sun has released an introductory article on Ant on their
  35. Dot-Com Builder site on May&#160;30&#160;2001. See <a
  36. href="http://dcb.sun.com/practices/profiles/ant.jsp">http://dcb.sun.com/practices/profiles/ant.jsp</a></p>
  37. </section>
  38. <section name="Ant 2.0 Requirements">
  39. <p>Ant has been in use for quite some time and has been used in ways never conceived when it
  40. was originally written. While Ant 1.x has continued to sucessfully evolve and grow, there
  41. are a number of limitations and inconsistencies that are now apparent and which need to
  42. be addressed.
  43. </p>
  44. <p>
  45. As we continue to evolve and enhance Ant 1.x, it is now time to define what Ant 2.0 will
  46. encompass. Ant 2.0 will be a major rearchitecting of Ant. It has a number of goals including:
  47. <ul>
  48. <li>Define the "contract" with build file writers to which Ant will be bound.</li>
  49. <li>Define the "contract" between the Ant core and Task writers.</li>
  50. <li>Make Ant more easily extendable by allowing additional tasks to be "dropped" in.</li>
  51. <li>Allow Ant to function as a component to simplify integration with GUIs and IDEs.</li>
  52. <li>Make Ant more regular and logical.</li>
  53. </ul>
  54. It is expected that Ant 2.0 will break Ant 1.x based build files. The intention is to
  55. make this the last time that will happen.
  56. </p>
  57. <p>
  58. To advance the definition of Ant, user requirements are now being accepted on the
  59. Ant-Dev mailing list. Any requirement will be accepted for consideration. The
  60. requirements are being collected into a document which is available
  61. <a href="ant2/requested-features.txt">on-line</a>. New features will be excepted
  62. until March 21st, 2001. At that time, each requirement will be discussed
  63. for inclusion in an Ant 2.0 requirement document.
  64. </p>
  65. <p>
  66. For your reference some of the goals which have shaped the development of Ant 1.x are
  67. available <a href="ant2/original-specification.html">here</a>. These continue to be
  68. relevant to Ant 2.0.
  69. </p>
  70. <p>
  71. If you want to shape the future of Ant, join the
  72. <a href="http://jakarta.apache.org/site/mail.html">Ant-Dev mailing list</a> and contribute
  73. your ideas.
  74. </p>
  75. </section>
  76. </body>
  77. </document>