Hi Martina, You're right: the problem is that with every Oxygen release, the set of jar files which need to be included for a transformation scenario changes, because version numbers change (Saxon 9 to 10 to 11, for instance), other files are modified (the Oxygen folks like to create their own patched versions of common tools such as jing, with different filenames), and new features are added to Oxygen which depend on new jars which were not there before. So with every Oxygen release, they update the list of jars in each transformation to match the files shipped with the current release. Our problem with the plugin is that we're trying to support multiple Oxygen versions, so we need to tweak our includes using wildcards to make sure we cover everything in such a way that transformations will work with various older versions of Oxygen. Cheers, Martin On 2022-10-17 07:27, Scholger, Martina (martina.scholger@uni-graz.at) wrote:

Dear Martin, dear all,

Thanks Martin for keeping an eye on the latest Oxygen releases. I agree that we need regular meetings with the Oxygen team. I can get in touch with them. Who would be interested in getting involved?

For now: how do we proceed? If I understand Alex's comment from today correctly, the references in *.framework to certain jar versions cause problems, or?

Best, Martina

-----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Martin Holmes Gesendet: Freitag, 14. Oktober 2022 17:55 An: TEI Council Betreff: [Tei-council] Oxygen plugin update

Hi all,

It turns out that we can't just adopt the new framework files provided by Radu. What we need to do is to compare each feature/transformation in the three current framework files with the new framework files, and figure out how to update each of our configurations based on the Oxygen ones; I'm really not sure what that will involve, and I don't have time to do it now, so I think it's time for Council to step in on this ticket:

https://github.com/TEIC/oxygen-tei/issues/27

I'm going to tentatively schedule some time next Friday to look at this if no-one else is interested, but until then I won't really be able to work on it, so be aware that if you update to Oxygen 25 and you're subscribed to the stable or bleeding-edge plugin, things may break. We might want to warn users too through TEI-L.

I thought we had managed to convince the Oxygen team that we really need plenty of warning when they're going to release a new version that will break things for us, but they don't seem to have got the message. It's not really in their interest, of course -- our plugin enables people to keep using old Oxygen versions and still have up-to-date TEI and Stylesheets, so I can see how that might not be something they're too keen on. But we also have mutual interests that are not being properly tended; it makes no sense for Oxygen to release a new version with baked-in TEI 4.4.0 when we're just a couple of weeks away from releasing 4.5.0. I think it would help if Council had a more formal relationship with the Oxygen team and held regular coordination meetings.

Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day.