On Sat, Mar 30, 2002 at 12:25:28PM +0000, Paul Hammant wrote:
...
> Fine by me, but I am deliberately being the newbie at the moment. Just
> doing "ant" at the root of axcalibur after a completely clean
> checkout/update.
>
> [javac] Compiling 10 source files to
> C:\Apache-CVS-UPD\jakarta-avalon-excalibur\concurrent\build\classes
> [javac]
>
>C:\Apache-CVS-UPD\jakarta-avalon-excalibur\concurrent\src\test\org\apache\avalon\excalibur\concurrent\test\ReadWriteLock
> TestCase.java:10: package junit.framework does not exist
> [javac] import junit.framework.TestCase;
>
> The ant.properties.sample file refers to:
> # ----- JUnit Unit Test Suite, version 3.7 or later -----
> junit.home=${base.path}/junit3.7
> junit.lib=${junit.home}
> junit.jar=${junit.lib}/junit.jar
>
> It does not refer to the relative junit....... :-(
>
> I will fix it unless someone else does or comes up with a justification....
Yes.. it's a bit annoying that, even though our dependencies are usually
within Avalon/Excalibur and we know the paths, users still have to 'cp
ant.properties.sample ant.properties'.
One solution would be to hardcode correct defaults in build.xml (see
all/build.xml).
A better solution, mimicking how the Turbine people do it, would be to
move *all* project properties out into project.properties, and source
that after ant.properties. For projects without external deps, users can
then just type 'ant'. It also makes the build.xml cleaner, and it's
easier to read the properties without all the XML tags.
I can implement this tomorrow if there's no objections.
--Jeff
> - Paul
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
