Björn Kautler

Codespan markers are not doubled when necessary

3

In some cases code span marker need to be doubled in AsciiDoc. When for example transforming `` `RegularFile`s ``, it must be transformed to ` ``RegularFile``s `, or it is...

Some code spans should be transformed with a pass macro or shorthand, depending on content

2

https://github.com/asciidoctor/kramdown-asciidoc does not translate all code spans 1:1 but sometimes uses `` `+the code here+` `` or `` `pass:c[the code here]` `` depending on the wrapped code. It does this...

Formatting in titles is sometimes lost

2

If you have formatting in a title like ```md ### `what.ever.Foo` ``` this gets lost during translation and ends up as ```adoc === what.ever.Foo ``` If there is other content...

The readme tells to use `nl.jworks.markdown_to_asciidoc:markdown_to_asciidoc:2.0.0`, but it now is `io.github.markdown-asciidoc:markdown-to-asciidoc:2.0.0`.

Spock 2.x support

3

The readme tells to use `@RunWith(ArquillianSputnik.class)`. That means to me, this is not compatible with Spock 2.x which is not JUnit 4 based anymore. Spock 2.x is a JUnit 5...

As the title says. I only see a CR release, which I guess means "candidate release". Will there ever be a final release for this? :-)

See https://youtrack.jetbrains.com/issue/IDEA-319527/Tool-windows-without-icon-are-very-hard-to-spot-in-new-ui, and please accordingly fix the plugin to somehow be visible.

Serialize tests during coverage calculation

12

Depends on #90 Fixes #73 Fixes hcoles/pitest#760 This generically fixes hcoles/pitest#760 and #73 for all platform engines, removing the Jupiter specific work-around from #74 and serializing test execution during coverage...

Depends on #91

Undividable Test Units

3

I'm sorry if this is not an issue with JUnit 5, but I'm not sure what the point with the old logic was, so I'm not sure how to test...