> I haven't looked at the code in question, but I would > think the hardest part of this whole effort would be > providing the means for Ant to look up antlib version > info. I'm actually fairly enthusiastic about using > the combination of existing arguments, mostly just > because of the number of requests I've seen for the > proliferation of arguments to Ant. Surely one of the > existing committers could hook that up if you don't > want to tackle that part, Jeff... again, the rest is > the tricky part IMHO!
I'm using META-INF/services from the JAR spec, so the discovery is actually pretty easy so long as the Antlibs are available via the classloader that oata.launch.Launcher configures. Note that this approach does not need a project: it will discover anything that's available from the classloader. I already have a similar function working in the extensions we use to build WebSphere, so I've just been adapting that. I had to reverse engineer the ServiceLoader class from JDK 6, since I know that I can't depend on a JDK 6 runtime. I could have used sun.misc.Service, but I figured that would be problematic on opensource JDKs. If someone else is willing to work on the command line stuff that would be appreciated: I don't feel comfortable enough with the codebase to be making major changes in that part of the code.
