[BUILD-STABLE]: Job 'PLC4X/PLC4X Build-Tools/develop [develop] [2]'

2019-06-24 Thread Apache Jenkins Server
BUILD-STABLE: Job 'PLC4X/PLC4X Build-Tools/develop [develop] [2]': Is back to normal.

[BUILD-FAILURE]: Job 'PLC4X/PLC4X Build-Tools/develop [develop] [1]'

2019-06-24 Thread Apache Jenkins Server
BUILD-FAILURE: Job 'PLC4X/PLC4X Build-Tools/develop [develop] [1]': Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X%20Build-Tools/job/develop/1/";>PLC4X/PLC4X Build-Tools/develop [develop] [1]"

Re: [DISCUSS] [CodeGen] Move the core generator modules to a separate git repo

2019-06-24 Thread Christofer Dutz
Hi all, so I just had infra create the new repo. Tomorrow I'll try to import the subdirectory of the plc4x-git into the new repo so we keep the history. Chris Am 24.06.19, 11:38 schrieb "Strljic, Matthias Milan" : Hi Chris, so i am not that creative 😃 and the name sounds quite

RE: [DISCUSS] [CodeGen] Move the core generator modules to a separate git repo

2019-06-24 Thread Strljic, Matthias Milan
Hi Chris, so i am not that creative 😃 and the name sounds quite functional ! 😊 +1 Greetings Matthias Strljic, M.Sc. Universität Stuttgart Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Seidenstraße 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax:

Re: [DISCUSS] [CodeGen] Move the core generator modules to a separate git repo

2019-06-24 Thread Julian Feinauer
Sorry for being that late (just missed that one). I am strongly for this split as ist really seperated code with other lifecylce. So my +1 is for sure! J Am 19.06.19, 20:54 schrieb "Christofer Dutz" : Hi all. So I have split up the parts of the code generator, that need to be exte