When we moved to Pure odd, all datatypes were cloned, purified, and renamed, data.foo becoming teidata.foo. it was recently agreed to deprecate the old versions for two years before killing them. Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: Kevin Hawkins Date:2016/11/07 02:44 (GMT+00:00) To: tei-council@lists.tei-c.org Subject: Re: [tei-council] Fwd: Jenkins build is unstable: TEIP5-dev #2602 Looking at http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/lastUnstableBuild/console , I see the following: validateodd: [echo] Validate tei_tite.odd as ODD [xslt] Processing /var/lib/jenkins/jobs/TEIP5-dev/workspace/P5/Exemplars/tei_tite.odd to /dev/null [xslt] Loading stylesheet /var/lib/jenkins/jobs/TEIP5-dev/workspace/P5/p5odds.message.isosch.xsl [xslt] [xslt] WARNING: reference to deprecated macro — 'data.word' will be removed from the TEI on 2018-10-01. [xslt] (concat(normalize-space(@key), normalize-space(@name)) eq 'data.word' / nonfatal) I guess you guys at some point deprecated data.word in P5. To figure out what it was replaced with, I'm looking around at https://github.com/TEIC/TEI/issues?utf8=%E2%9C%93&q=is%3Aissue%20data.word but am unclear on which of these refers to whatever action was taken. Could someone point me in the right direction? If the change doesn't raise any obvious questions for Tite, you should feel free to make the change directly without me being involved. I don't think Martin H. receives emails to tei-council, so if you'd like him to take action, you'll need to nudge him separately. Kevin On 11/4/16 10:48 AM, Lou Burnard wrote:
They are deprecation warnings so we should call the attention of the maintainers to the need to fix them: kevin for tire; Martin h for jtei.
Sent from my Honor Mobile
-------- Original Message -------- Subject: [tei-council] Fwd: Jenkins build is unstable: TEIP5-dev #2602 From: Hugh Cayless To: TEI Council CC:
So this is because of all the new warnings about refs to old (pre-Pure) datatypes in Exemplars. The offenders seem to be Tite and JTEI. Is it ok to just fix those? Or should we live with the errors? Or set Jenkins to ignore them? If we're really deprecating them, presumably we should fix the exemplars...
Hugh
---------- Forwarded message ---------- From: Victoria TEI Jenkins
Date: Fri, Nov 4, 2016 at 8:52 AM Subject: Jenkins build is unstable: TEIP5-dev #2602 To: James.Cummings@it.ox.ac.uk, mholmes@uvic.ca, tei-council@lists.tei-c.org, philomousos@gmail.com, stadlerpeter@yahoo.fr, noreply@github.com, lou.burnard@retired.ox.ac.uk http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/2602/ -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived