some utilities for other scripting language projects.

These would be better expressed as macros, but I'm just doing housecleaning on uncommitted files right now and would rather have something imperfect committed than lose track of it entirely.
no longer import language-specific extensions by default.  projects previously relying on this for java will now need to include the java extensions file after the main exus build file.
doc location doesn't belong under target.  autogenerated api docs might seem to, but I'll leave that to invidual projects to decide on a strategy for; meanwhile, you should certainly have other kinds of docs than autogenerated api docs, and they should be committed, not under the target heading!
decompose exusInit target into several targets for varying levels of initial layout.  the exusInit target depends only on the most minimal layout target; layout appropriate for projects with platform specific resources are no longer created by default.
add a not-so-subtle hint to default project layout that you should consider clearly denoting your various layers of test approach (an idea borrowed from the rails community).
make nested tags on exusJavac and exusJavacStrict optional.

the `<classpath refid="path" />` pattern is almost certainly a better idea than `depends="${toString:path}"`, so it's likely nested tags will be used the majority of the time, but there's no need to be insistent about it.
make nested tags on exusPack optional.
remove the creation of subdirectories under ${target} in exusInitLayout; these have been outmoded since the adjustment to put all outputs under ${target}.

also, projects are likely to have varying opinions on these dirs.  The java-specific extension as of recently began laying out compilation results under a dedicated subdir of ${target} by default, for example, and there's no reason to expect a python project to be interested in quite the same convention.