Dmitry Baev

or we can use `withPotentialTimeout` only if there are no `Timeout` rules present and get timeout from annotation in `Timeout` otherwise

There are problems with timeout architecture - two different ways to specify timeouts, with different behavior. Using `ThreadLocal` we add one more implicit (kind of magic?) relation. Maybe this solution...

@7170 take a look http://allure.qatools.ru

@vlsi can we provide a possibility to override output per task?

ok, the issue is that you setting allure commandline version (using `version.set(allureVersion)`), but not updating allure-java version (`allureJavaVersion.set(allureVersion)`). So the following will work: ``` allure { version.set(allureVersion) adapter { allureJavaVersion.set(allureVersion)...

can't reproduce the problem. Allure Maven plugin uses the same version of java that maven did

Maybe the problem is that you are uses bundled Maven from IDE?

btw Allure TestOps has it's own labels-from-tags processing: try to add tag `@allure.id=123` or `@allure.label.layer: api` For report users there is no point to add custom labels as everything custom...

the main idea is that Allure reporter inits state and then users may modify the state within a test: ```js it('simple test', function () { allure.step('check A', function () {...

BTW at the moment we are already have helper that simulates that behaviour using `to_jsonb` function: ```java public static Field toJsonb(final Table table) { return field( "to_jsonb({0})", SQLDataType.JSONB.asConvertedDataType(new JooqJsonb2RecordConverter(table)), table...