On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart <gscok...@gmail.com> wrote: > Did you have any example to demonstrates the benefits of such task ?
The benefits with conjunction with <import> could be important, in that you can "mix-in" specialized pre-defined builds dealing with specific concerns (like JAXB pre-compilation for example) and have those builds "implicitly" augment the classpath or Javac source path appropriately for example (as documented in those builds, and you do explicitly import those, so are kinda in control). Sure, it does open the door for some complexity, and Ant would enter some un-chartered waters indeed, but when trying to design reusable builds in the (distant now) past, I've often felt the need for such a feature. Yet it doesn't necessarily mean that would have been the right solution either. I'd be interesting to have the input of the EasyAnt people on the matter in fact. Maybe an opt-in approach, explicitly adding final="false" on those datatype ids *designed* for extension, would be a more conservative introduction of this feature, although that does force to have "perfect hindsight" into what will be necessary to extend/augment or not. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
