BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [94]':
Is back to normal.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [93]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/93/;>PLC4X/PLC4X/develop
[develop] [93]"
Hi Chris,
Done with option a)
Lukas
Am Fr., 16. Okt. 2020 um 16:32 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:
> Hi Lukas ...
>
> Just in case you didn't see it:
>
> [WARNING] Files with unapproved licenses:
>
>
Hi Lukas ...
Just in case you didn't see it:
[WARNING] Files with unapproved licenses:
src/site/resources/images/users/companies/logo_record_evolution_single_dark_bgfont.svg
Could you please do one of the following:
a) Replace the SVG with a PNG
b) Ask if we can get a version with an
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [92]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/92/;>PLC4X/PLC4X/develop
[develop] [92]"
Hi all,
Thanks @Chris and @Katharina
I edited the adopters page (added Record Evolution) and added the Record
Evolution Logo to our git repository.
https://github.com/apache/plc4x/blob/develop/src/site/asciidoc/users/adopters.adoc
Once again thank you :)
Kind regards
Lukas
Am Fr., 16. Okt.
Hi Lukas,
Katharina approached me directly and I asked her to send the information to
this list.
I do know that PRs might sort of be a challenge for non-developers, so I
thought if the request goes to this list, It's on officially on file too, which
should be enough.
Unfortunately the
Hi Katharina,
That is completely fine for us.
Can you do a pull-request on Github:
https://github.com/apache/plc4x/blob/develop/src/site/asciidoc/users/adopters.adoc
and add Record Evolution via Pull request in the adoc-file.
This is our way to go - so we have a recorded confirmation - that you
Hello everyone,
I am writing to you because of your list of companies using Apache PLC4X
and wanted to ask if you could add Record Evolution GmbH.
I checked your current list and you can find the according information on
Record Evolution below:
You can find the Record Evolution *logo* attached
hutcheb merged pull request #194:
URL: https://github.com/apache/plc4x/pull/194
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
chrisdutz merged pull request #192:
URL: https://github.com/apache/plc4x/pull/192
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
Hi Ben ...
So do you want to merge your PR? It would really be useful to have that stuff
in develop ...
Chris
Am 16.10.20, 10:16 schrieb "Ben Hutcheson" :
Hi Chris,
I have included a getBooleanArray() in each of the PlcBYTE, WORD, DWORD and
LWORD classes. The refactor PR
Hi Chris,
I have included a getBooleanArray() in each of the PlcBYTE, WORD, DWORD and
LWORD classes. The refactor PR should be ready.
Adding getBitLength and getBit methods seem like they could be useful.
kind Regards
Ben
On Fri, Oct 16, 2020 at 3:44 AM Christofer Dutz
wrote:
> Hi all,
>
>
Hi all,
I’m currently working on porting the PlcValues to Go and here just stumbled
over something.
The PlcBYTE, PlcWORD, PlcDWORD seem to be integer values and not allow
accessing the bool values as bit-fields.
I know Ben is still working on his improvements … will this be covered here? Do
Hi Folks,
so in the plc4go branch I did the changes and all of the adjustments in the
tests this change needed.
In the end it seems I needed to go down the "test-jar" path as "provided"
resources don't seem to be included in the default classpath and I therefore
couldn't load them.
But with
Hi Lukasz,
could you possibly whip up a proposal in a branch ... I have to admit I don't
quite understand the problem you're trying to solve.
Perhaps being able to see what changes you propose makes this easier?
Chris
Am 14.10.20, 18:19 schrieb "Łukasz Dywicki" :
Hey all,
I have a
This is another reason I would really like to get rid of netty ... it's no
longer doing very much in our drivers (is more a relic from the pre 0.7-times).
I think as soon as I have the SPI working for Go we could think of back porting
that structure to Java and to eliminate Netty all together.
17 matches
Mail list logo