> From: Siberski, Wolf [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 5 July 2000 18:19 > To: '[EMAIL PROTECTED]' > Subject: Subpackages of ...taskdefs.optional (was: RE: [PATCH]: Path, > Execution framework, JUnit and JavaCC) > > > That wouldn't help because we would get as many subpackages > as we have optional tasks now; what would we gain by introducing > subpackages then?. > As I'm no ant developer I'm reluctant to make a complete proposal > here. But IMHO the tasks should be put in more general packages. > E.g. I would put all EJB related tasks in a .ejb package, all > version control tasks in a .sccm package, etc. > If this is not enough, one could add subpackages for the > different products, e.g. .ejb.wls, .ejb.inprise, .sccm.cvs, > .sccm.pvcs, ... >
+1 I had reached a similar conclusion and I am intending to add my weblogic tasks under optional.ejb
