Antoine Levy-Lambert wrote: > Can you give us some pointers so that we can learn about these > Extension-Name and Extension-List elements and understand how they help > out for antlib ?
http://java.sun.com/j2se/1.4.1/docs/guide/jar/jar.html#Main%20Attributes http://java.sun.com/j2se/1.4.1/docs/guide/extensions/versioning.html Servlet 2.3+ required containers to support this, there are many servers that use this information, many packages already include a manifest and are starting to support this. I'm not saying this is perfect - but it is a reasonable and standard solution, and better than us inventing our own. >> It defines a hook that allows you to plug your own component factory. >> You get a namespace and element name as parameter, and you can return >> any ProjectComponent. >> >> It is used like the PropertyHelper ( i.e. a chain, any task can add > hooks ). >> >> Nothing fancy. >> > Can you supply some Hello World examples of what can be done with the > ComponentHelper task or give us pointers to such examples. I'll try to add more documentations and an example. >> I have no problem with using XML syntax and not properties- if it's a > subset >> of ant, or something close enough. I'm -1 on combining antlib with >> roles and using the syntax in the proposal. >> >> > Which problem do you see with this notion of roles ? For me it is clear. Look - adding "roles" concept to ant, and adding antlib are 2 separate issues. If everyone else except me wants to add "roles" - and doesn't want to use interfaces, but explicit declarations - I could change my vote to -0 on roles. Using XML for descriptor - fine, as long as it is not a completely new format. Using a subset of ant is IMO a very good solution, and it would allow us to easily enhance it later on. Mixing roles with antlib proposal - that's where I'm strongly -1. Costin
