> From: Steve Loughran [mailto:[EMAIL PROTECTED] > > I dont actually want packages, see. Instead I want a > directory that you > can -lib to that pulls in all the various project-independent > declarations. > > Then I can run ant > > ant -lib /projects/smartfrog/antbuild/core > > And get everything in there. Currently that is ant-contrib > and a version > of maven artifacts I compiled myself yesterday. Then I can go > xmlns:antlib://checkstyle.xml > xmlns:antlib://emma.xml > and get all the relevant declarations pulled in, without > having to put > my unpackaged stuff into subdirs, jar files, etc, etc. >
Not sure I understand what Steve is trying to do. But it looks like one issue that we have not been able to resolve satisfactorily (on my mind) with the current way antlibs get loaded. Lets assume we completely abandon the property files that we currently use to declare the tasks belonging to core (including optional tasks), and move to an antlib based world. Now, for backward compatibility and for convinience in general, one would like to be able to put in the -lib directories a bunch of antlib jars and that all their tasks get declared automatically as part of the default name space. This without requiring any declarations on the project files. You have them because they are part of your installation. It will be fine for me if one needs to add something in the jar that makes them "auto-installable" it could be some special value in the manifest, or some other thing like the way JAVA services work. That will allow people to create either auto-installable antlibs or manually declared ones. It is up to the packager to decide. So, any ideas how this could be acomplished? Jose Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
