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

On 15-02-04 08:46 AM, James Cummings wrote:

Actually my manage add-ons screen lists Oxygen Version 15.2+ so there might be something in the current framework that is requiring even later oxygen.

The current stable release version of the plugin actually requires 15.2, I think, so that should probably be updated. Cheers, Martin

Glad my guide was helpful... do point people you know using oxygen (post 14+) to it as it is a really good way to get the tei framework updated.

-James

On 04/02/15 16:30, Raffaele Viglianti wrote:

...

Ok - just come across James's guide: http://blogs.it.ox.ac.uk/jamesc/2014/04/02/auto-update-your-tei-framework-in...

Add on frameworks are available from version 14+, so I'll get that Oxygen 16 license :)

On Wed, Feb 4, 2015 at 11:18 AM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:

...

Hi Martin,

Is there a Oxygen version requirement to try this out? I'm currently running 13... but will get an upgrade to 16 soon. Also, related: is it worth having my department getting me a license for 16 or is 17 coming out soon?

Raff

On Wed, Feb 4, 2015 at 11:16 AM, Martin Holmes wrote:

...

Thanks Fabio! Anyone else willing to subscribe? If a few of us are using it, we'll notice when anything goes wrong. Advantages: get all the latest and greatest features of the Stylesheets and P5. Disadvantages: might break sometimes, but you can always roll back to a previous version.

<http://teijenkins.hcmc.uvic.ca/job/oxygen-tei/ lastSuccessfulBuild/artifact/oxygen-tei/updateSite.oxygen>

Cheers, Martin

On 15-02-04 07:09 AM, Fabio Ciotti wrote:

...

Ok, pom.xml disappeared. I've tried things here and there and everything seems to work...

f

2015-02-04 0:50 GMT+01:00 Martin Holmes :

...

Fixed it! Fabio, try updating your plugin, and you shouldn't see that "pom.xml" any more.

Cheers, Martin

On 15-02-03 01:19 PM, Martin Holmes wrote:

> I can see that pom.xml file appearing in the build, but I'm not sure > where it's coming from. It seems to be something to do with the P5 > build > that gets pulled in. Sebastian, do you recognize it? pom.xml ends > up in > templates/TEI P5. > > Cheers, > Martin > > On 15-02-03 11:12 AM, Fabio Ciotti wrote: > >> Hi Martin and all, >> >> in my Oxy (Ubuntu Linux version) using the experimental Jenkins >> build >> of the framework I find a misleading "pom" (Mavent project file >> coming I guess from Jenky) type of TEI file in the open new file >> dialog box. >> >> Fabio >> >> 2015-02-03 17:52 GMT+01:00 Martin Holmes : >> >>> Hi all, >>> >>> I now have a development build of the oxygen-tei add-on >>> working. You >>> can >>> subscribe from here: >>> >>> >>> <http://teijenkins.hcmc.uvic.ca/job/oxygen-tei/ >>> lastSuccessfulBuild/artifact/oxygen-tei/updateSite.oxygen> >>> >>> >>> If you're brave enough to try it, uninstall the regular version of >>> the >>> add-on before installing this one. >>> >>> I can also confirm that James was right: you can provide access to >>> multiple >>> versions of the plugin, allowing people to roll back to a previous >>> version >>> if something breaks, by providing multiple xt:extension >>> elements in >>> the >>> updateSite.oxygen file. This seems to be working well with the URL >>> above: >>> if, when you're subscribing to the plugin (Help / Install New >>> Add-Ons) you >>> uncheck the "Show only the latest versions of the add-ons", you'll >>> see there >>> are three versions available. I have it set up so we'll keep >>> the last >>> ten >>> versions available. >>> >>> I've subscribed myself, so I should be able to see if anything >>> goes >>> wrong. >>> If you do test it, be aware that if you have transformation >>> scenarios >>> (for >>> instance) that depend on the absolute location of the TEI >>> extension >>> framework, those paths will no longer work; Oxygen stores the >>> add-on >>> data in >>> a path which includes a modified version of the URL of the >>> updateSite.oxygen >>> file. It's easy to change back to the standard TEI release, >>> though. >>> >>> A new version of the plugin will be built and "released" every >>> time >>> the >>> Stylesheets or P5 are rebuilt; the former triggers the latter, >>> so the >>> overall process takes quite a while, but the build of the >>> oxygen-tei >>> plugin >>> itself takes only a few seconds. >>> >>> I'm copying Sebastian on this because my Jenkins is still >>> reporting >>> build >>> failures and successes to him, as the Oxford one does to me, and I >>> want to >>> confirm that this should continue (or if it shouldn't, then what >>> should >>> happen instead). I'd also like to get this setup working on the >>> Oxford >>> Jenkins so we have some redundancy. >>> >>> The next step is to create some tests we can run in Oxygen to >>> check >>> core >>> functionality of the add-on. I envisage this as an Oxygen project >>> with a >>> bunch of sample files that are transformed or otherwise >>> manipulated >>> and the >>> results checked. These files would presumably live in the >>> oxygen-tei >>> repo. >>> >>> Cheers, >>> Martin >>> -- >>> 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

-- 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