vert-x3 / vertx-ext-parent Goto Github PK

The maven jacoco plugin requires a slightly different configuration of the surefire plugin to inject the Jacoco Agent attachment.

The following configuration should be ok:

<argLine>${argLine} -server -Xmx1200M</argLine>

Then, jacoco compute it's own argLine prepended to the surefire configuration.

Vert.x ext components now process any asciidoc file in src/main/asciidoc to target/asciidoc, allowing to migrate from package-info.java file to plain asciidoc files.

Hello,

I encounter a problem to execute unitary test with IntelliJ since v17 of vertx-ext-parent due to a message "Erreur : impossible de trouver ou charger la classe principale @{surefireArgLine}".
With v15 of vertx-ext-parent, i was able to execute unit test in IntelliJ without problem.

console with v15:

D:\Java\jdk1.8.0_11\bin\java -ea -Dio.netty.leakDetectionLevel=PARANOID -Didea.launcher.port=7535 "-Didea.launcher.bin.path=D:\JetBrains\IntelliJ IDEA Community Edition 14.1\bin" -Dfile.encoding=windows-1252 -classpath "D:\JetBrains\IntelliJ IDEA Community Edition 14.1\lib\idea_rt.jar;...1\json-20090211.jar" com.intellij.rt.execution.application.AppMain com.intellij.rt.execution.junit.JUnitStarter -ideVersion5 io.vertx.ext.marklogic.MarklogicClientWriteTest,write_single_xml_document
Starting test: MarklogicClientWriteTest#write_single_xml_document 

Process finished with exit code 0

console with v17:

D:\Java\jdk1.8.0_11\bin\java -ea -Dio.netty.leakDetectionLevel=PARANOID -server -Xmx1200M @{surefireArgLine} -Didea.launcher.port=7537 "-Didea.launcher.bin.path=D:\JetBrains\IntelliJ IDEA Community Edition 14.1\bin" -Dfile.encoding=windows-1252 -classpath "D:\JetBrains\IntelliJ IDEA Community Edition 14.1\lib\idea_rt.jar;D:\JetB...1\json-20090211.jar" com.intellij.rt.execution.application.AppMain com.intellij.rt.execution.junit.JUnitStarter -ideVersion5 io.vertx.ext.marklogic.MarklogicClientWriteTest,write_single_xml_document
Erreur : impossible de trouver ou charger la classe principale @{surefireArgLine}

Process finished with exit code 1

Several users have reported a lack in the current documentation. We never give the Maven / Gradle dependency information in the manuals. We definitely should.

So, here is the first step. In order to not hard-code the information in the documentation, we can let asciidoctor to replace some placeholders by the right values.

For instance:

 * .Maven
 * [source,xml,subs="+attributes"]
 * ----
 * <dependency>
 *   <groupId>{maven-groupId}</groupId>
 *   <artifactId>{maven-artifactId}</artifactId>
 *   <version>{maven-version}</version>
 *</dependency>
 * ----

Notice the subs="+attributes" enabling the substitution in code block (disabled by default).

In some projects it can be useful to override this property so that multiple folders can be used. The default value of this property would be ${asciidoc.dir}/*.adoc

The Maven clean plugin is configured to delete the src/main/asciidoc directory. It should also delete the src/main/generated directory, so that mvn clean compile creates a "fresh" view of generated classes.