Execution jcabi-qulic e-check of goal com.qulice:qulice-maven-plugin:0.22.0:check failed. about qulice

[yegor256]

@MikhailLipanin don't attach log file, paste log right into the body of the ticket

[MikhailLipanin]

@yegor256 done

[OlesiaSub]

@yegor256 any progress here?

[yegor256]

@Graur maybe you can help?

[Graur]

@OlesiaSub @MikhailLipanin @yegor256 Right now we have a workaround: maven-compiler-plugin cannot work with different java versions at the same time.
I'll try to add a readable error message about this to qulice.

[MikhailLipanin]

@OlesiaSub @Graur @yegor256 this helped me, may be it is a solution

[Graur]

@MikhailLipanin You are right, but it's a workaround solution. We need some handler to get a readable message in such cases

[l3r8yJ]

@Graur I also encountered this problem and this is what helped me
in pom.xml we have to set 1.8 version

      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.8.1</version>
        <configuration combine.self="override">
          <source>1.8</source>
          <target>1.8</target>
          <compilerArgs>
            <arg>-Xpkginfo:always</arg>
          </compilerArgs>
        </configuration>
      </plugin>

  <properties>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
  </properties>

[volodya-lombrozo]

@Graur @MikhailLipanin Do you have any possible solution here? It looks like we faced with the same problem. We can not just put 11 java version for <source> and <target> sections.

[yegor256]

@Graur maybe you can help?

[volodya-lombrozo]

I had the same problem with org.ow2.asm:asm:9.5 dependency check. (I got the same exception.)
The next configuration helped me:

<exclude>dependencies:.*</exclude>

It is a workaround, of course

[l3r8yJ]

@volodya-lombrozo we ported quilice to java 17, it seems to be working fine

you can take a look here

[volodya-lombrozo]

@l3r8yJ How can I use qulice with java 17? I checked the both README files from qulice and qulice17 repos. They seem identical. Moreover the maven group id and artifact id are the same.

[l3r8yJ]

@volodya-lombrozo I think @h1alexbel can help us here, don't you?

[h1alexbel]

@l3r8yJ @volodya-lombrozo we need to update the groupId and publish it to maven central

[volodya-lombrozo]

@h1alexbel @l3r8yJ I created an issue for that eo-cqrs/qulice17#37

[h1alexbel]

@volodya-lombrozo thanks