Adam R. B. Jack wrote:
Perhaps we should make both available.
Hmm, what if we have both in one file?
<antlib>
<taskdef name="stamp"
classname="org.apache.depot.version.ant.stamp.VersionMarkerGeneratorTask"/>
<taskdef name="version-stamp"
classname="org.apache.depot.version.ant.stamp.VersionMarkerGeneratorTask"/>
I don't know what happen in the case of a clash (I see version-available
already exists this way, not as available) but I assume the first takes
over.
I changed that because it was overriding the standard available type.
So having both does not solve the problem of conflicts.
If/when namespaces get restored we'll need uses to change to version: so
having version- isn't so bad, is it? Having users change their resource file
seems intrusive.
Lest use version- for now.
When names spaces are available we can create in the terse version.
The point is when used with name spaces use wont want to write
version:version-stamp. and since they will be adding the name space
declaration they can add the -terse suffix to the file name if they want
to use the shorter task names.
Thoughts?
regards