Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

build error by 2024.1.14 and 2024.1.13 #584

Open
zcfire2017 opened this issue May 7, 2024 · 12 comments
Open

build error by 2024.1.14 and 2024.1.13 #584

zcfire2017 opened this issue May 7, 2024 · 12 comments

Comments

@zcfire2017
Copy link

image

image

image

2024.1.12 version sucess
@rsmckinney
Copy link
Member

I’ll need to see the code that is causing the error. You can see the stack trace by selecting the top item in the build results list. I’ll need that as well. Thanks

@dakotahNorth
Copy link

dakotahNorth commented May 7, 2024 •
edited

I recently upgraded to 2024.1.14 and the Json and RuntimeMethods API is not available!?

            Object jsonObj = Json.fromJson(jsonString);
            return RuntimeMethods.coerce(jsonObj, targetClass);

As highlighted here ... #572

Plus ... the JSON schema is not showing up as a Java object.

Gradle file

       ext {
          springCloudVersion = '2023.0.1'
          manifoldVersion = '2024.1.14'
       }
     
      dependencies {

          implementation "systems.manifold:manifold-json-rt:${manifoldVersion}"
          annotationProcessor "systems.manifold:manifold-json:${manifoldVersion}"
          testAnnotationProcessor "systems.manifold:manifold-json:${manifoldVersion}"
      
      }

@rsmckinney
Copy link
Member

@dakotahNorth I cannot reproduce this issue locally. Is this an IntelliJ issue in the editor, or is this a compile error from the build? In either case, if you haven't already, please reload your project and see if the error persists. If it does, I would like to either have access to your project, or if that is not possible, if you could create a minimal project that displays the issue, that would help a great deal. Thanks.

@rsmckinney
Copy link
Member

@dakotahNorth Here is a sample project that uses the example you provided and uses release 2024.1.14. It works for me. Please test this in your environment. Thanks.

bug584.zip

@zcfire2017
Copy link
Author

`PS D:\work\java\kc-ai\admin-api> mvn -e package
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] --------------------------< com.kc:admin-api >--------------------------
[INFO] Building admin-api 1.0-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ admin-api ---
[INFO] Copying 7 resources from src\main\resources to target\classes
[INFO]
[INFO] --- compiler:3.12.1:compile (default-compile) @ admin-api ---
[INFO] Recompiling the module because of changed source code.
[INFO] Compiling 194 source files with javac [debug target 17] to target\classes
编译器 (17.0.8.1) 中出现异常错误。如果在 Bug Database (https://bugs.java.com) 中没有找到该错误，请通过 Java Bug 报告页 (https://bugreport.java.com) 建立该 Java 编译器 Bug。请在报告中附上您的程序、以下诊断信息以及传递到 Java 编译器的参数。谢谢。
com.sun.tools.javac.code.Symbol$CompletionFailure: 找不到org.openxmlformats.schemas.officeDocument.x2006.docPropsVTypes.STVectorBaseType的类文件
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] An unknown compilation problem occurred
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.558 s
[INFO] Finished at: 2024-05-08T08:42:47+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.1:compile (default-compile) on project admin-api: Compilation failure
[ERROR] An unknown compilation problem occurred
[ERROR]
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.1:compile (default-compile) on project admin-api: Compilation failure
An unknown compilation problem occurred

at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)

Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
An unknown compilation problem occurred

at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1269)
at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:212)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)

[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
`

@rsmckinney
Copy link
Member

rsmckinney commented May 8, 2024 •
edited

Thanks @zcfire2017. Unfortunately, the actual stack trace is missing, only the error message is reported:

com.sun.tools.javac.code.Symbol$CompletionFailure: 找不到
org.openxmlformats.schemas.officeDocument.x2006.docPropsVTypes.STVectorBaseType的类文件

Might I have access to your project so I can debug the issue? Otherwise, I don't know how to reproduce this. Thanks.

@dakotahNorth
Copy link

dakotahNorth commented May 8, 2024 •
edited

@dakotahNorth I cannot reproduce this issue locally. Is this an IntelliJ issue in the editor, or is this a compile error from the build? In either case, if you haven't already, please reload your project and see if the error persists.

I had reloaded it a few times, but of course when I went back to try it again after reading your note, it worked. : )

Thank you!

@rsmckinney
Copy link
Member

@zcfire2017 if your project is not available, one other option toward fixing this issue would involve you capturing the compiler exception on your machine. I can walk you through the steps to make that happen. Essentially, it just involves debugging the build from intellij and making an exception breakpoint on Symbol.CompletionFailure. When the debugger stops at the breakpoint, you would dump the stack frame and take note of what statement/expression is causing it. That information should be enough for me to understand where the issue is. Would greatly appreciate your cooperation here. Thanks!

@zcfire2017
Copy link
Author

@rsmckinney

I think it may be because of the problem of project reference. I have a basic project and there is no problem in using it. Then the basic project will be installed in the local warehouse. My other projects will reference this basic package, and then other projects that reference this basic package will only The 2024.1.12 version can be used, but an error will be reported when upgrading to 2024.1.13 or 2024.1.14.

@zcfire2017
Copy link
Author

@rsmckinney

I think it may be because of the problem of project reference. I have a basic project and there is no problem in using it. Then the basic project will be installed in the local warehouse. My other projects will reference this basic package, and then other projects that reference this basic package will only The 2024.1.12 version can be used, but an error will be reported when upgrading to 2024.1.13 or 2024.1.14.

Of course, not all modules in the project are reporting errors. There are three modules in my project, and only one of them will fail to generate. I guess it may be due to the use of tuples

@rsmckinney
Copy link
Member

@zcfire2017 thanks for the info. Do you have a stack trace or is your project available? It would help a lot toward diagnosing the problem. I'd like to fix the issue asap. Thanks.

rsmckinney added a commit that referenced this issue May 20, 2024
@rsmckinney
https://github.com/manifold-systems/manifold/issues/584
bfd7fa5 
- changes that may help diagnose this issue
@rsmckinney
Copy link
Member

@zcfire2017 please try release 2024.1.16. I still can't reproduce this issue, however based on the issue beginning with 2024.1.13, I am attempting to isolate the problem by process of elimination. Please let me know what, if any, changes come about from this release. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rsmckinney @dakotahNorth @zcfire2017