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.

index.xml 2.6 kB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. <document>
  2. <properties>
  3. <author email="">Conor MacNeill</author>
  4. <title>Mutant Introduction</title>
  5. </properties>
  6. <body>
  7. <section name="Introduction">
  8. <p>
  9. These pages describe the design and implementation of Mutant.
  10. </p>
  11. <p>
  12. For some time, there has been the concept of Ant 2.0, a rearchitecting of
  13. Ant designed to address the shortcomings in the design of Ant 1.x, while
  14. drawing the experience gained in that development. This rearchitecting
  15. would most likely be accompanied by at least some break in backward
  16. compatability. Over time Ant 2.0 has come to be known as Ant2 and the current
  17. Ant codebase is generally known as Ant1.
  18. </p>
  19. <p>
  20. Mutant is my proposal, a revolution, for Ant2. Actually, I consider it more
  21. an evolution of the design and implementation used for Ant1, but in Jakarta
  22. parlance, being a separate codebase, it is termed a revolution.
  23. </p>
  24. <p>
  25. There is no special significance in the name Mutant. I chose it because, as
  26. a word, it is an extension of the word Ant and it also signifies a change
  27. from the previous generation
  28. </p>
  29. </section>
  30. <section name="Other Proposals">
  31. <p>
  32. Mutant is not the only proposed revolution for Ant2. Peter Donald has
  33. developed another known as
  34. <a href="http://jakarta.apache.org/ant/myrmidon">Myrmidon</a>
  35. which presents a different view of how Ant2 could be realized. Other
  36. people hold the view that Ant1 can continue to evolve and that there
  37. is no need for rearchitecture of its codebase. I recommend you
  38. investigate all these points of view.
  39. </p>
  40. <p>
  41. As I write this, no decision has been taken as to which codebase will be
  42. adopted for Ant2. It may not be Mutant and it could even be some entirely
  43. new proposal. These pages do not compare and contrast Mutant with these
  44. other proposals or points of view, at least not explicitly. They are just
  45. intended to describe how Mutant is designed and implemented and why it is the
  46. way it is.
  47. </p>
  48. </section>
  49. <section name="Getting Started">
  50. <box>
  51. <h1><font color="red">Caution</font></h1>
  52. <p>
  53. Mutant is not even an alpha release. While it is relatively stable, it is
  54. subject to change. There are no backward compatability guarantees for any of
  55. the classes, interfaces, build files, configuration, launch scripts, etc that
  56. Mutant provides.
  57. </p>
  58. <p>In particular, some features in Mutant are experimental and may not, in the
  59. long run, prove to be worthwhile.</p>
  60. </box>
  61. <p>
  62. <a href="goals.html">Start</a> now by looking at the key requirements which have
  63. shaped the design of Mutant.
  64. </p>
  65. <div align="right">
  66. <p>Conor MacNeill</p>
  67. </div>
  68. </section>
  69. </body>
  70. </document>