Hi Lukasz,
thank you very much for your help, I will look into this today.
For the drivers as services, isn't that already the case? I know that for
S7 and EIP at least,
the yhave the osgi.cmpn dependency and the @Component annotation for the
class, as well as a file with the implemented Driver
I haven't used Camel for a while, but to me it seems to be a problem
caused by caller's classloader.
See that in stack trace you have a thread which is started by camel, so
there are 3 or even 4 classloaders to be considered:
- plc4x, definitely not a faulty one
- netty, could be troublesome but
Let's not introduce yet another way to do such things ... these annotations
seem to work fine and we/I've used them all over the place to make the
testsuite runnable in all sorts of different scenarios.
So-far we have:
- RequireInternetConnection
- RequireNonCaptureAllDns
- RequirePcap
-
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [826]':
Is back to normal.
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [822]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/822/;>PLC4X/PLC4X/develop
[develop] [822]"
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [821]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/821/;>PLC4X/PLC4X/develop
[develop] [821]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [820]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/820/;>PLC4X/PLC4X/develop
[develop] [820]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [819]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/819/;>PLC4X/PLC4X/develop
[develop] [819]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [818]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/818/;>PLC4X/PLC4X/develop
[develop] [818]"
Lukas Ott created PLC4X-190:
---
Summary: Support for umati: universal machine technology interface
Key: PLC4X-190
URL: https://issues.apache.org/jira/browse/PLC4X-190
Project: Apache PLC4X
Issue
Also one can use „assumeThat()“ in junit for such things.
> Am 06.04.2020 um 10:25 schrieb Julian Feinauer :
>
> Nice, then thats the way to go!
>
> Am 06.04.20, 10:21 schrieb "Christofer Dutz" :
>
>I've already got an annotation you can use:
>@RequirePcap together with a Junit
Why not DOTNOT? :-)
Cheers,
Łukasz
On 03.04.2020 16:33, Bjoern Hoeper wrote:
> Some people are masochistic... ;)
> Joking aside I think the more relevant option is F# which could be a good
> match for some use cases
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz
> Gesendet:
Nice, then thats the way to go!
Am 06.04.20, 10:21 schrieb "Christofer Dutz" :
I've already got an annotation you can use:
@RequirePcap together with a Junit Condition, that skips the test if the
condition is not met ... just noticed a bug in my condition however __ ... just
fixing
I've already got an annotation you can use:
@RequirePcap together with a Junit Condition, that skips the test if the
condition is not met ... just noticed a bug in my condition however __ ... just
fixing it.
Chris
Am 06.04.20, 10:11 schrieb "Julian Feinauer" :
Hey,
I would not
Hey,
I would not choose 1, as you say.
Perhaps we can make this tests conditional (dont know how easy this is with
junit5) an das you say, only allow releases with libpcap.
Julian
Am 06.04.20, 10:07 schrieb "Christofer Dutz" :
Hi,
I’m currently working on the prerequisiteCheck
Hi,
I’m currently working on the prerequisiteCheck for my new plc4c module and am
testing on empty OSes (OSes without any installed additional software)
I noticed there are tests like the Raw-Socket test that naturally fail if you
don’t have libpcap (or the windows counterpart installed) …
We
16 matches
Mail list logo
