seaside1
seaside1
Can you check the conflict in JRuleEngine? (Came with last merged PR)
It's not building though. I get this when merging against origin main: ``` [19:04:52] josha@zool:~/git/jrule-pr-194-startup-level> git pull --rebase origin main From https://github.com/seaside1/jrule * branch main -> FETCH_HEAD Auto-merging src/main/java/org/openhab/automation/jrule/internal/engine/JRuleEngine.java CONFLICT...
Sorry for the mess, I was merging JRuleEngine at the same time as you @querdenker2k I think it is ok now, except its failing for some test. Last one was...
Not sure, unfortunately I'm not using MDC tags atm. Probably something we should fix before next release.
I'll see if I can set it up again and test.
@rsopp Can you help to check this? I can't see anything apparent in the dynamic build PR, to me the MDC-tags looks similar as before
Adding ` @JRuleTag(value = "TESTTAG") ` On a testrule, and adding ``` JRuleLog.debug(logger, context.getLogName(), "setting mdc tags: {}", context.getLoggingTags()); Arrays.stream(context.getLoggingTags()).forEach(tag -> logInfo("mdc: using tag in context: {}", tag)); ``` The...
Nice to see the interest in this. Already today there are mechanisms in place for detecting changes to rules or items and the reload JRule. I would be fairly simple...
Personally I wouldn't use that feature. The generated jar is not worth storing in that sense for me. It can be regenerated easily and I tend to share it by...
Some good suggestions. - Yes would be fairly simple to check the external jars and to a reload when they are changed - It would be possible to store a...