Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

1.37.0 throwing exceptions ... 1.36.1 works

已關閉
#1,478 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
55/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
java
領域
tooling

研究方向

Start by reproducing the failure with the provided Maven configuration, comparing google-java-format 1.37.0 with 1.36.1 on the reported Java file. The issue gives no repository test or failing formatter entry point, so first inspect how the project exercises formatter versions and captures exceptions. Done means identifying and fixing the cause of the exception, with a regression check for the reported version.

由索引模型根據 Issue 內容生成。

描述

Starting with 1.37.0 I started getting these errors on every file:

src/test/java/com/xxx/xxx/xxx/xxx/xxx/starter/testing/SimpleTypeRepository.java:LINE_UNDEFINED google-java-format(java.lang.reflect.InvocationTargetException) java.lang.reflect.InvocationTargetException (...)
Resolve these lints or suppress with <lintSuppressions>
at com.diffplug.spotless.maven.SpotlessApplyMojo.process (SpotlessApplyMojo.java:121)
at com.diffplug.spotless.maven.AbstractSpotlessMojo.execute (AbstractSpotlessMojo.java:288)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:127)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:336)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:324)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:220)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:181)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:79)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:169)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:166)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:106)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:74)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:121)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:267)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:179)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:1017)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:299)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:219)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
at java.lang.reflect.Method.invoke (Method.java:580)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)

      <plugin>
        <groupId>com.diffplug.spotless</groupId>
        <artifactId>spotless-maven-plugin</artifactId>
        <version>3.10.4</version>
        <configuration>
          <java>
            <includes>
              <include>src/it/java/**/*.java</include>
              <include>src/main/java/**/*.java</include>
              <include>src/test/java/**/*.java</include>
            </includes>
            <googleJavaFormat>
              <version>1.37.0</version>
              <style>GOOGLE</style>
            </googleJavaFormat>
          </java>
        </configuration>
      </plugin>

主要語言
Java
星號
6.2k
分支
940
平均合併
7 小時 46 分鐘
30 天內合併 PR
11

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

google/google-java-format 的其他 Issue

查看 google/google-java-format 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。