HI James, On 15-02-04 08:36 AM, James Cummings wrote:
I've removed my old TEI P5 add on and installed this one. It downloaded and installed fine, oXygen restarted.
It is confusing because the schemas referenced in the xml-model of course point to the current release, but behind the scenes it is using a copy of the schema downloaded from Jenkins. right?
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?
I tried to think of a way to test this and then I remembered global @resp.
So mine seems to have updated seamlessly. Just waiting for an additional schema-changing thing to trigger an update... so I can update. The next question is whether we should be using precisely the same version 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: 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.
A possible problem:
When I go to Help -> Manage add-ons and *uncheck* both "show only compatible add-ons" and "show only latest versions of the add-ons" I get a list of versions 2.7.10, 2.7.9, 2.7.8 etc. but the status of all the earlier ones is 'Incompatible'. Any ideas why so?
My guess is because you already have the latest one installed; if you removed it, they would all be compatible. Cheers, Martin
-James