Apologies if folks are already pursuing something like this, or have
considered and rejected it, but I figured I'd toss it out and see how
quickly it sank...
I've been noticing that while most of the Apache projects I've played with
include a routine that can return the version number of the package --
which is wonderful -- they aren't remarkably consistant about where that
routine is kept.
java org.apache.xalan.processor.XSLProcessorVersion
org.apache.xerces.framework.Version
and so on.
Might it make sense for everyone to converge upon a single standard
org.apache.xerces.Version
org.apache.xalan.Version
... etc., perhaps all implementing a shared abstract-version API that lives
in the "commons" package? And perhaps to do something equivalent for the
C++ code, if it has the same scattering of solutions?
I'm not dogmatic about exactly what that API should look like, as long as
it's consistant. I'd be willing to settle for a main() that printed a
version string on stdout (for convenient checking from the command line)
and a getVersion() which returned that string so applications could report
which level they were running against.
If we wanted to get fancy about it, we could make the subfields of the
string individually retrievable -- which would allow applications to test
exactly what they were running against and perhaps apply workarounds for
specific versions. But I think that's more complication than we really need
right now.
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
