|
From: Colin S. <col...@ex...> - 2004-01-05 17:06:24
|
A few days ago I changed the build to make the taskdef for the attribute compiler use a classpath to bring in these needed jars, instead of relying on the user to add them to the ant lib dir. Generally it can cause complications/problems to add libs directly to the ant lib dir, and best avoided if at all possible. For example, if you add xjavadoc.jar there, then you have to add all the other xdoclet modules there as well, if you want to use xdoclet elsewhere. There seem to be no issues with this approach, with both ant 1.6 and 1.5... Rod Johnson wrote: >The tests now depend on a Commons Attributes precompile step. However, this >doesn't take very long at all as it applies only to one package. > >However, you will need to put the following files in your $ANT_HOME/lib to >get the tests to run: > >- Commons Attributes compiler Jar (in CVS) >- commons-collections.jar (in CVS) >- xjavadoc.jar (from XDoclet project). I'm not sure whether to put this in >CVS as none of our code uses it. Thoughts? > >For now, I've named the attributes-dependent test case so that Eclipse won't >pick up. I'll change this when I get time so that the build is also >triggered under Eclipse. > >Regards, >Rod > > |