[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [318]'

BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [318]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/318/;>PLC4X/PLC4X/develop [develop] [318]"

[BUILD-STABLE]: Job 'PLC4X/PLC4X/develop [develop] [319]'

BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [319]': Is back to normal.

Re: [DISCUSS] Generate a standalone executable version of the maven-plugin and build tools?

My impression was that we checked in the code so that we could review the code / code generation changes in github, not because of a lack of automation. I don’t see what this would give us that we don’t have, other than being in a different shiny way. Can you elaborate more on the problem

AW: [DISCUSS] Generate a standalone executable version of the maven-plugin and build tools?

Hi Otto, well generally it's considered bad practice to commit generated code. Especially in this case it mixes up with the real code. Yes: It also has the benefit of us being able to review code and I remember we used to use that for this in the early days of PLC4C. Sebastian made the code

[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [315]'

BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [315]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/315/;>PLC4X/PLC4X/develop [develop] [315]"

AW: DF1 protocol ...cant find documentation

Hi Gaurav, yeah ... Lukas you beat me to it :-) Yes .. in the "protocols" directories in the root of the PLC4X repo, we have the protocol specifications. These are used for all driver variants we have or are working on (Currently there's code-generation for: Java, Go, C, C#) ... these specs

[DISCUSS] Generate a standalone executable version of the maven-plugin and build tools?

Hi, last week I managed to do some cool stuff with GraalVM compiling a Java Application into a windows executable. Now I was thinking ... wouldn't this also work for our Maven plugin? Of course, we probably need to add something to it or to create a new module that uses the template engine and

[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [314]'

BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [314]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/314/;>PLC4X/PLC4X/develop [develop] [314]"

[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [316]'

BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [316]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/316/;>PLC4X/PLC4X/develop [develop] [316]"

[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [317]'

BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [317]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/317/;>PLC4X/PLC4X/develop [develop] [317]"