Reproducer for 'tycho-compiler-jdt unable to compile test code when module-info.java is present' / Issue 230 #809

jason-faust · 2022-03-27T04:03:59Z

Demonstration of the problem reported in issue #230

laeubi · 2022-04-08T07:43:38Z

@jason-faust this change seems to include a lot of unrelated changes, can you rebase it and only submit relevant changes?

jason-faust · 2022-04-09T17:00:34Z

@laeubi Which branch do you want it to target? 2.7 or master?

laeubi · 2022-04-09T17:52:54Z

master please, if suitable we can backport it later on.

jason-faust · 2022-04-10T00:52:42Z

Hopefully this works.

laeubi · 2022-04-10T05:24:52Z

Is this the error you are expecting?
https://ci.eclipse.org/tycho/job/tycho-github/job/PR-809/2/testReport/org.eclipse.tycho.test.compiler/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/
according to the debug output java 1.7 level is used: -target, 1.7, -source, 1.7

jason-faust · 2022-04-10T15:37:33Z

That is the error, but a little lower down in the output. There may also be some follow on issues with the compiler plugin passing along the source and target options when it should only be passing the release option, but that is unrelated to the current issue.

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.099 s
[INFO] Finished at: 2022-04-10T01:12:18Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile (default-testCompile) on project c.m.m: Fatal error compiling: Unrecognized option : --patch-module -> [Help 1]

laeubi · 2022-04-10T16:04:44Z

Can you try to force target/source to 11 just to see if this changes anything?

jason-faust · 2022-04-10T16:59:40Z

Testing locally has the same error when using source, test, and release at 11.

github-actions · 2022-04-10T18:32:58Z

Unit Test Results

151 files 151 suites 1h 1m 28s ⏱️
259 tests 255 ✔️ 3 💤 0 ❌ 1 🔥

For more details on these errors, see this check.

Results for commit 8d696d6.

♻️ This comment has been updated with latest results.

laeubi · 2022-04-13T08:25:30Z

@mickaelistria @akurtakov any one has an idea whats wrong here? Is this an EJC issue?

mickaelistria · 2022-04-13T09:50:48Z

Indeed, it looks like the tycho-compiler-jdt doesn't support the --patch-module option that the maven-compiler-plugin is passing it. I'm not sure what's the "wronger" here: maven-compiler-plugin passing this option, or tycho-compiler-plugin not reading it.

laeubi · 2022-04-18T06:19:52Z

So any jdt / maven compiler expert who can help here?

laeubi · 2022-04-18T06:22:51Z

For the record, here is the full commandline passed to jdt and the error message:

[INFO] Compiling 1 source file to /home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/target/test-classes
[DEBUG] JDT compiler args: [--patch-module, ex=/home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/target/classes:/home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/src/test/java:/home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/target/generated-test-sources/test-annotations:, --add-reads, ex=ALL-UNNAMED, -s, /home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/target/generated-test-sources/test-annotations, -d, /home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/target/test-classes, -classpath, /home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/target/test-classes, /home/runner/work/tycho/tycho/tycho-its/target/projects/MavenCompilerPluginTest/testMavenCompilerPluginModuleWithTests/compiler.mavenCompilerPlugin.moduleWithTests/src/test/java/ex/ATest.java, -g, -nowarn, -target, 11, -source, 11, --release, 11]
[DEBUG] Original compiler output: Unrecognized option : --patch-module

laeubi · 2022-08-10T04:58:34Z

@iloveeclipse can you tell if tycho is doing anything wrong here or if this is a user error?

iloveeclipse · 2022-08-10T05:12:52Z

I'm not a module expert. Spec is here: https://openjdk.org/jeps/261

If you would attach source code in a project with configuration as it is expected to work plus the actual command line that triggers ECJ, it would simify debugging.

laeubi · 2022-08-10T05:15:28Z

The code is here: https://github.com/eclipse-tycho/tycho/tree/8d696d614a95000438b379bdeb41f2e0d9f322e7/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests
The JDT compiler arguments generated by Tycho is here: #809 (comment)
Original compiler output: Unrecognized option : --patch-module

If I understand @jason-faust correctly javac can compile this?

iloveeclipse · 2022-08-10T05:29:36Z

If you would attach source code in a project with configuration as it is expected to work

I really meant exact that above. Not some random files somewhere, but as a proect with compiler settings.

laeubi · 2022-08-10T05:51:59Z

I'm not sure if one can transform this into an eclipse project, this uses maven to replace the javac compiler by using ejc (see here https://github.com/eclipse-tycho/tycho/blob/8d696d614a95000438b379bdeb41f2e0d9f322e7/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/pom.xml) so not a "traditional" eclipse project.

I think one can emulate this by

Download the zip: https://github.com/eclipse-tycho/tycho/archive/8d696d614a95000438b379bdeb41f2e0d9f322e7.zip and extract it to e.g. /tmp/tycho-bug
Create a Java main file (I just put it into the jdt.core bundle)

public class CallCompiler {

	public static void main(String[] args) {
		String basePath = "/tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/";
		Main.compile(
				"--patch-module ex=" + basePath
		                + "target/classes:" + basePath + "src/test/java:" + basePath
		                + "target/generated-test-sources/test-annotations: --add-reads ex=ALL-UNNAMED -s "
		                + basePath
		                + "target/generated-test-sources/test-annotations -d "
		                + basePath
		                + "target/test-classes -classpath " + basePath
		                + "target/test-classes " + basePath
		                + "src/test/java/ex/ATest.java -g -nowarn -target 11 -source 11 --release 11");

	}

}

laeubi · 2022-08-10T05:59:24Z

By the way javac says:

javac --patch-module ex=/tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/target/classes:/tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/src/test/java:/tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/target/generated-test-sources/test-annotations: --add-reads ex=ALL-UNNAMED -s /tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/target/generated-test-sources/test-annotations -d /tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/target/test-classes -classpath /tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/target/test-classes /tmp/tycho-bug/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/src/test/java/ex/ATest.java -g -nowarn -target 11 -source 11 --release 11
error: option --source cannot be used together with --release
error: option --target cannot be used together with --release
Usage: javac <options> <source files>
use --help for a list of possible options

If I remove those, ejc still complains Unrecognized option : --patch-module but javac fails with;

error: module not found: ex
1 error

So I maybe messed up the call a bit but maybe it still helps as ejc is not getting over the parsing options stage....

laeubi · 2022-08-28T10:17:00Z

@iloveeclipse is the provided example suitable? Is this a bug I should report to JDT?

akurtakov · 2022-09-15T15:25:23Z

Would you please fix the conflict with master?

mickaelistria · 2022-09-15T20:29:21Z

By the way, the documentation of maven-compiler-plugin and other discussions recommends

      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <compilerId>eclipse</compilerId>
        </configuration>
        <dependencies>
          <dependency>
            <groupId>org.codehaus.plexus</groupId>
            <artifactId>plexus-compiler-eclipse</artifactId>
            <version>...</version>
          </dependency>
          <dependency>
            <groupId>org.eclipse.jdt</groupId>
            <artifactId>ecj</artifactId>
            <version>...</version>
          </dependency>
        </dependencies>
      </plugin>

So if this works, then I don't think Tycho should support the use-case you describe here and the jdt compiler should be treated as an internal artifact of Tycho, not to be mixed with the maven-compiler-plugin.

laeubi · 2022-09-16T05:19:23Z

So if this works, then I don't think Tycho should support the use-case you describe here and the jdt compiler should be treated as an internal artifact of Tycho, not to be mixed with the maven-compiler-plugin.

Probably its the other way round, if plexus-compiler-eclipse is a standard compiler API interface maybe Tycho should then drop its own wrapper to the compiler and use the same path as maven-compiler-plugin? If not it seems there are benefits of the Tycho one and is an equally valid choice than the suggested approach.

stephan-herrmann · 2024-01-22T17:43:26Z

[DEBUG] Original compiler output: Unrecognized option : --patch-module

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=526110#c3

The compiler has support for the option, just the batch compiler doesn't parse it (and the above got forgotten due to little demand ...)

laeubi · 2024-01-22T17:54:08Z

@stephan-herrmann thanks for the insight, so should I open a bug at JDT or is there already an issue that tracks it?

stephan-herrmann · 2024-01-22T18:00:56Z

@stephan-herrmann thanks for the insight, so should I open a bug at JDT or is there already an issue that tracks it?

No issue in github yet, so please create one, and link also to the old bugzilla, thanks, which can then be closed as MOVED (with another link).

laeubi · 2024-01-22T18:06:43Z

Depends on

[batch compiler] Unrecognized option : --patch-module eclipse-jdt/eclipse.jdt.core#1895
new eclipse release after the fix

laeubi · 2024-02-12T08:37:29Z

@jason-faust can you try out if using javac instead of ecj fixes the problem for you:

https://github.com/eclipse-tycho/tycho/blob/main/RELEASE_NOTES.md#using-javac-as-the-compiler-for-tycho

jason-faust · 2024-02-12T13:26:59Z

@laeubi That won't fix my problem as I want to be able to use the Eclipse compiler. I ultimately want to be able to generate the same compiler warnings and errors that the Eclipse IDE will generate, so to use the same compiler, not to use a different compiler.

laeubi · 2024-02-12T13:30:44Z

@laeubi That won't fix my problem as I want to be able to use the Eclipse compiler. I ultimately want to be able to generate the same compiler warnings and errors that the Eclipse IDE will generate, so to use the same compiler, not to use a different compiler.

You can at least validate if it actually can work :-)

jason-faust · 2024-02-12T13:38:54Z

@laeubi The issue is about the JDT plugin to the maven compiler plugin, not the tycho compiler.

laeubi · 2024-02-12T13:49:55Z

@laeubi The issue is about the JDT plugin to the maven compiler plugin, not the tycho compiler.

So does it compile if you use javac maven compiler?

jason-faust · 2024-02-23T20:46:32Z

@laeubi

Updated to fix the merge conflict. And if you remove the call out to the jdt from the test pom.xml, it does build.

stephan-herrmann · 2024-02-23T21:05:44Z

@laeubi

Updated to fix the merge conflict. And if you remove the call out to the jdt from the test pom.xml, it does build.

It would be interesting to know the exact options which maven passes into javac.

jason-faust · 2024-02-23T22:02:07Z

@laeubi
Updated to fix the merge conflict. And if you remove the call out to the jdt from the test pom.xml, it does build.

It would be interesting to know the exact options which maven passes into javac.

From the test output (excerpt)
[DEBUG] JDT compiler args:

--patch-module ex=<paths>
--add-reads  ex=ALL-UNNAMED
-s <paths>
-d <dir>
-classpath <paths>
-g
-nowarn
-target 1.7
-source 1.7
--release 17

stephan-herrmann · 2024-02-23T23:00:06Z

@laeubi
Updated to fix the merge conflict. And if you remove the call out to the jdt from the test pom.xml, it does build.

It would be interesting to know the exact options which maven passes into javac.

From the test output (excerpt) [DEBUG] JDT compiler args:

Thanks. Just to be sure: these are the arguments that work with javac (it says JDT here)?

In those args source, target and release don't seem to match (1.7 != 17), but other than that I don't see anything magic, so fixing --patch-module for ecj should be enough to resolve this.

laeubi · 2024-06-08T13:55:20Z

@srikanth-sankaran can you maybe help her as you recently worked on the compiler a lately, this seems to be the relevant JDT issue if I correctly understand:

[batch compiler] Unrecognized option : --patch-module eclipse-jdt/eclipse.jdt.core#1895

laeubi · 2024-09-10T10:03:46Z

As it is now fixed (thanks to @stephan-herrmann ) hopefully this update will make it finally work:

Bump org.eclipse.jdt:ecj from 3.38.0 to 3.39.0 #4240

laeubi · 2024-09-12T10:01:34Z

For some reasons it assumes a wrong target level now

org.codehaus.plexus.compiler.CompilerException: target level should be in '1.8','9'...'22' (or '8.0'..'22.0'): 1.7

Strange enough the pom says

<configuration>
  <compilerId>jdt</compilerId>
  <release>17</release>
</configuration>

laeubi · 2024-09-13T03:38:26Z

@jason-faust if I specify

<source>17</source>
<target>17</target>

compile proceeds (this seems to be due to the default values passed by maven compiler plugin, not sure if one should ignore source / target if release is given).

But then the compilation fails with

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile (default-testCompile) on project c.m.m: Compilation failure
[ERROR] tycho/tycho-its/projects/compiler.mavenCompilerPlugin.moduleWithTests/src/test/java/ex/ATest.java:[1] 
[ERROR] 	package ex;
[ERROR] 	        ^^
[ERROR] ex cannot be resolved to a module
[ERROR] 1 problem (1 error)

so it seems the inital problem is solved, do you want to adjust the testcase and fix the compile error(s) so we can merge it?

jason-faust · 2024-09-13T15:46:47Z

@laeubi The test case is still correct as far as I can tell. If you comment out the <compilerId>jdt</compilerId> option to get the test to run using the javac compiler the test will pass.

Tycho is not passing down a --module-path option that the stock maven compiler passes that refers to target\classes

Stock maven compiler plugin command line options sent (paths shortened for readability):

-d target\test-classes
-classpath target\test-classes;
--module-path target\classes;
-sourcepath src\test\java;target\generated-test-sources\test-annotations;
-s target\generated-test-sources\test-annotations
-g
-nowarn
-target 17
-source 17
--patch-module ex=target\classes;src\test\java;target\generated-test-sources\test-annotations;
--add-reads ex=ALL-UNNAMED

Tycho compiler plugin command line options sent (paths shortened for readability):

--patch-module ex=target\classes;src\test\java;target\generated-test-sources\test-annotations;
--add-reads ex=ALL-UNNAMED
-s target\generated-test-sources\test-annotations
-d target\test-classes
-classpath target\test-classes
src\test\java\ex\ATest.java
-g
-nowarn
-target 17
-source 17

The Tycho plugin not handling <release> on it's own is a different issue.

akurtakov · 2024-09-13T16:12:29Z

I have never considered tycho-compiler-jdt as a compiler backend for maven-compiler-plugin nor ever tried it. Have you tried https://mvnrepository.com/artifact/org.codehaus.plexus/plexus-compiler-eclipse if you rely on maven-compiler-plugin?

jason-faust · 2024-12-11T19:12:14Z

Have used the plexus compiler before but that one makes use of the -log argument, which prevents capturing a log file for further use. If the JDT supported multiple instances of the -log argument that would solve the issue and let the plexus compiler be used.

stephan-herrmann · 2024-12-11T20:03:19Z

I'm unsubscribing for now

jason-faust changed the base branch from master to tycho-2.7.x March 27, 2022 04:08

jason-faust force-pushed the issue_230_reproducer branch from 75b5cdb to e112aa2 Compare April 10, 2022 00:50

jason-faust changed the base branch from tycho-2.7.x to master April 10, 2022 00:50

mickaelistria closed this Apr 13, 2022

mickaelistria reopened this Apr 13, 2022

laeubi mentioned this pull request Sep 15, 2022

Move to Java 17 as runtime JVM #983

Closed

laeubi changed the title ~~Issue 230 reproducer~~ Reproducer for 'tycho-compiler-jdt unable to compile test code when module-info.java is present' / Issue 230 Sep 16, 2022

laeubi mentioned this pull request Jan 22, 2024

[batch compiler] Unrecognized option : --patch-module eclipse-jdt/eclipse.jdt.core#1895

Closed

laeubi marked this pull request as draft January 22, 2024 18:06

jason-faust force-pushed the issue_230_reproducer branch from 2ba1368 to 8a28264 Compare February 23, 2024 20:43

jason-faust marked this pull request as ready for review February 23, 2024 20:48

laeubi force-pushed the issue_230_reproducer branch from 8a28264 to af12e0d Compare September 12, 2024 05:37

laeubi force-pushed the issue_230_reproducer branch from af12e0d to bdfc70e Compare September 12, 2024 16:07

jason-faust force-pushed the issue_230_reproducer branch from bdfc70e to cde1d67 Compare September 13, 2024 15:53

Minimal test for issue 230

00ed182

laeubi force-pushed the issue_230_reproducer branch from cde1d67 to 00ed182 Compare November 4, 2024 09:31

Reproducer for 'tycho-compiler-jdt unable to compile test code when module-info.java is present' / Issue 230 #809

Are you sure you want to change the base?

Reproducer for 'tycho-compiler-jdt unable to compile test code when module-info.java is present' / Issue 230 #809

Conversation

jason-faust commented Mar 27, 2022

laeubi commented Apr 8, 2022

jason-faust commented Apr 9, 2022

laeubi commented Apr 9, 2022

jason-faust commented Apr 10, 2022

laeubi commented Apr 10, 2022

jason-faust commented Apr 10, 2022

laeubi commented Apr 10, 2022

jason-faust commented Apr 10, 2022

github-actions bot commented Apr 10, 2022 • edited Loading

Unit Test Results

laeubi commented Apr 13, 2022

mickaelistria commented Apr 13, 2022

laeubi commented Apr 18, 2022

laeubi commented Apr 18, 2022

laeubi commented Aug 10, 2022

iloveeclipse commented Aug 10, 2022

laeubi commented Aug 10, 2022 • edited Loading

iloveeclipse commented Aug 10, 2022

laeubi commented Aug 10, 2022 • edited Loading

laeubi commented Aug 10, 2022

laeubi commented Aug 28, 2022

akurtakov commented Sep 15, 2022

mickaelistria commented Sep 15, 2022

laeubi commented Sep 16, 2022

stephan-herrmann commented Jan 22, 2024

laeubi commented Jan 22, 2024

stephan-herrmann commented Jan 22, 2024

laeubi commented Jan 22, 2024

laeubi commented Feb 12, 2024

jason-faust commented Feb 12, 2024

laeubi commented Feb 12, 2024

jason-faust commented Feb 12, 2024

laeubi commented Feb 12, 2024

jason-faust commented Feb 23, 2024

stephan-herrmann commented Feb 23, 2024

jason-faust commented Feb 23, 2024 • edited Loading

stephan-herrmann commented Feb 23, 2024

laeubi commented Jun 8, 2024

laeubi commented Sep 10, 2024

laeubi commented Sep 12, 2024

laeubi commented Sep 13, 2024

jason-faust commented Sep 13, 2024

akurtakov commented Sep 13, 2024

jason-faust commented Dec 11, 2024

stephan-herrmann commented Dec 11, 2024

github-actions bot commented Apr 10, 2022 •

edited

Loading

laeubi commented Aug 10, 2022 •

edited

Loading

laeubi commented Aug 10, 2022 •

edited

Loading

jason-faust commented Feb 23, 2024 •

edited

Loading