Jeff,
>
>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.
>
Well Pete has good objections.
I'd prefer some forced warning with a suggestion of a couple of remedy
rather than just getting a compile error. If the use feels they are
making progress, then they will continue:
"Hi the compile of Exacilibur classes cannot happen without
the the presence of the JUnit for the comiple env. You may
eithether 1) put junit.jar in ant's lib directory, 2) rename the
the ant.properties.sample file in excaliburs root dir or 3) run
the 'get-junit' target. After any of those try the failing ant
target again. Thanks for you patience."
- Paul
>
>
>--Jeff
>
>>- Paul
>>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
