On Mon, Jun 14, 2010 at 2:06 AM, Stefan Bodewig <bode...@apache.org> wrote: > Since that method is final (at > least in 1.8.0) you can't even override it.
Yea, can we talk about this? It seems like there is a lot of places where ant discourages people from being able to override stuff. Is there a good reason for that? > You don't really want to use refid because this is meant to say a given > type is just a placeholder for something defined anywhere else. In your > case you just need to use a different name for the attribute (say > reference instead of refid) and just use Ant's reference system for all > the rest - don't make your baseclass think the instance was just a > placeholder. Yep, that is pretty much what I ended up doing. I had to write my own recursive tree [1] which seems to be working well enough for a first shot. I've actually got things working now with an ant syntax that I'm happy with. I haven't had time to fully document things yet, but take a look at the example.xml file... http://code.google.com/p/sweetened/source/browse/trunk/example.xml You can now define a path to the jar, its source code as well as a scope in a single location in an ant build file. This is enough information to generate the .classpath/.project file for Eclipse as well as provide a single location to setup compile/javadoc/junit classpaths. All without having to learn or use Ivy or Maven (both of which fail the kiss test for me). I feel like this is functionality that has been missing in ant forever now. jon [1] http://code.google.com/p/sweetened/source/browse/trunk/src/com/googlecode/sweetened/typedef/SweetenedPath.java#55 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
