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.

antlib_roadmap.xml 1.5 kB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. <?xml version="1.0"?>
  2. <document>
  3. <properties>
  4. <index value="2"/>
  5. <author email="antoine@apache.org">Antoine Levy-Lambert</author>
  6. <title>Antlib Roadmap</title>
  7. </properties>
  8. <body>
  9. <section name="Antlib with tasks and types only">
  10. <p>
  11. Let me quote here Stefan Bodewig - April 24th 2003.
  12. </p>
  13. <p>
  14. Let's make a version of antlib that knows about two predefined roles,
  15. task and data-type. I think this is already feature complete in the
  16. proposal (which does even more).
  17. </p>
  18. <p>
  19. Let's move this code with the restriction to tasks and types into the
  20. main branch ASAP. Let's sort out the classloading requirements as
  21. well as the interplay of antlib with taskdef and typedef here.
  22. </p>
  23. <p>
  24. After this flies, I'd expect us to get roles sorted out. If we feel
  25. like removing the difference between tasks and types, we can do so
  26. then as well.
  27. </p>
  28. </section>
  29. <section name="Roles and components in build files">
  30. <p>
  31. A second step : make a detailed proposal concerning roles and implement roles and components in ant core.
  32. </p>
  33. </section>
  34. <section name="Roles and components in antlibs">
  35. <p>
  36. Once roles and components are properly defined and implemented in ant core, we would revisit &lt;antlib&gt; and implement roles and components there.
  37. </p>
  38. </section>
  39. <section name="Namespaces">
  40. <p>
  41. After we have antlibs, roles, and components, we should specify how we are going to proceed concerning namespaces and prefixes.
  42. </p>
  43. </section>
  44. </body>
  45. </document>