[tei-council] oxygen-tei package

[Peter Stadler]

Yes, rewriting the scripts seems (technically) not to be a big deal. But I’m still trying to understand what’s going on: 
There are 
* some parts original to the oxygen-tei package (icons, i18n, etc)
* some parts coming in from the TEI release
* some parts coming in from the Stylesheets release
* the java parts coming in from ? and depending on ?

The last item on the list made the build during release fail (to my knowledge). I wonder whether this part is (or: can be) maintained by the Council or whether it needs to be maintained by the oxygen people? 

Best
Peter

Am 19.09.2014 um 16:44 schrieb Sebastian Rahtz <sebastian.rahtz at it.ox.ac.uk>:

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20140919/14d3775c/attachment-0001.bin