Re: [tei-council] Development version of oxygen-tei plugin available

4 Feb 2015

      On 04/02/15 16:48, Martin Holmes wrote:
...
Yes, exactly. That's an inconsistency. We could re-work the 
build process so that it's pointing at Jenkins-based schemas, 
but that in itself is a little fragile. You don't want to be 
creating documents for the long term which point at schemas 
that are constantly changing. It's slightly complicated by the 
fact that if you link to a version of a known TEI schema (known 
to Oxygen), Oxygen often validates against the tei-c.org version.
What does the team think? What would be the ideal behaviour here?
Keep it as is but validate against the jenkins version of the 
schema.  That is what *seems* to be happening now. Presumably it 
only validates against the website when it can't find the other 
version? (At which point you have other problems because that is 
part of the framework it has downloaded...)
...
...
numbering -- What I'm wondering is whether there is some way 
to embed
the revision number in it.  Currently the version
That got cut off, but on the version number for the plugin:
Weird. Don't know why. I didn't say anything you didn't predict.
...
The first two digits come from the major and minor P5 versions 
(so 2.7). The overall number has to increment in order to allow 
updates to be different, so I just increment that last number 
with every build. The "official" release also has a relatively 
meaningless number for its third digit, I think (Sebastian will 
know). If anyone can think of another approach for this, it's 
easy to change.
Yes. What I'm suggesting is that you somehow incorporate the 
revision number of both SVN and GitHub.  Currently the 
updateSite.oxygen file for each extension has something like:

xt:version2.7.2

I'm suggesting that we change it to the much less human-readable 
for the public, but potentially useful for us:

xt:version2.7.0r13126-7.29.0rc5c16b9

So that then we could see *precisely* which version of both TEI 
P5 and Stylesheets we are using.

The problem comes if you tell me that xt:version has to be 
sequentially / numerically 'higher' than its predecessor....
...
My guess is because you already have the latest one installed; 
if you removed it, they would all be compatible.
You are entirely right. If I uninstall the current one I can then 
jump back to any of them. If only there was a clear relationship 
between the version number there and revisions in SVN  ;-)

-James

-- 
Dr James Cummings, James.Cummings@it.ox.ac.uk
Academic IT Services, University of Oxford