[tei-council] oxygen-tei package

[Sebastian Rahtz]

On 19 Sep 2014, at 15:23, Peter Stadler <stadler at edirom.de> wrote:

> As Martin noted (many thanks for the „Reflections on the release"), there had been some issues with the creation of the oxygen-tei package during the last release.
> I see some activity in the meantime in the oxygen-tei repo on Google Code and I have some questions, as I tried my way through the build process:
> 
> 1. Why is it on Google Code? Could we bring that project to GitHub as well?

Because it was set up by oxygen, and is used by them.  They’d have to be consulted.

> 2. The repo has kind of a weird structure to me as is the build process with two ant files and a shell script. I guess this is by evolution not by design (as Martin would say ;) ?
> 
I wrote the shell script on top of the ant build.xml (upper one no longer needed, just one left now), to get the thing working. you could probably
rewrite it all in pure Ant fairly easily.

> I think I’d like to rearrange things a little bit and merge all the tasks in one ANT file and source all parameters out to (local.)build.properties. I have never set up Jenkins tasks but to my knowledge ANT scripts play well with it? 

yes, sure.

> So, is anyone already working on it and what would be needed for Jenkins exactly?
> 

the simplest Jenkins task just runs a command. whether that be “make”, “ant”, “mvn” or whatever.

if you can express the job so that Jenkins just runs the command “ant”, you’re done. It monitors the
job for failures, and reads the output.

--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Não sou nada.
Nunca serei nada.
Não posso querer ser nada.
À parte isso, tenho em mim todos os sonhos do mundo.