Warning:No JDK specified for module

最新推荐文章于 2024-02-29 21:05:55 发布
原创 最新推荐文章于 2024-02-29 21:05:55 发布 · 1.7w 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了解决Android Studio中出现的unknownfacettypejavagradle错误的方法。该错误通常是由于缺少AndroidSupport插件导致的。解决步骤包括在设置中启用AndroidSupport插件并重启IDE。

unknown facet type javagradle



原因：缺少Android Support插件 
解决：进入File-》Settings-》Plugins 
勾选Android Support选项 
重启AS即可

【已解决】java: JDK isn‘t specified for module...
JavaPub
11-27 1214
没有指定 JDK,先配置一下 jdk。指定项目对应的 jdk 版本。
阿里云服务器使用记录2 尝试安装JDK+Tomcat
CoCoNutNut的博客
07-06 309
重置服务器N次后，放弃官网教程 尝试安装JDK+Tomcat 参考 https://blog.youkuaiyun.com/Wyx_wx/article/details/82712419 服务器环境 Ubuntu 16.04 64位 FileZilla连接服务器 官网下载安装FileZilla_3.43.0 填写公网IP、用户名、密码、端口 连接成功 上传文件 官网下载并上传： jdk-12.0...
Error:java:JDK isn‘t specified for module
HumorChen的博客
12-01 2532
解决：删掉项目中的.idea文件夹，然后关闭该项目，在idea中重新打开项目之后系统会自动重新生成.idea,此时新打开的项目会变成非maven项目,所以需要点击项目中的pom文件,右键 Add as Maven Project.错误：idea报错Error:java:JDK isn’t specified for module “模块名称”原因：项目中的.idea文件夹被删掉，或者修改项目内容后，重新生成的.idea有问题，导致项目目录出错。
Warning:No JDK specified for module "XXX"
cjhxydream的博客
05-29 2万+
配置项目的时候出现这种错误 解决步骤： 1.在project Structure 中选择相应的项目，把Source中的language level选项选择图中的选项 在Source中的language level选项修改后的结果如下 2.在project Structure 中选择相应的项目，把Dependencies中的Module SDK选择相应的jdk版本 修改后如下图 3.配置项...
No JDK specified for module ‘XXX‘
Comin的博客
10-31 1321
No JDK specified for module
解决：IntelliJ IDEA 2019.2.3 出现 Warning: No JDK specified for module错误
weixin_45439637的博客
05-27 1万+
问题： 运行后出现错误：Error running ‘ReformApplication’: No jdk for module ‘gmis-reform’ 这是一个子model，其他模块正常，这种问题可能是IDEA的问题，因为在别人的环境没有出现过。 解决方式： 总结：这个问题表面是没有JDK，但是配置完并没有作用，试了很多方式，最后重新导包后才解决；但是每次重启idea都需要重新导包，还会出现这样的问题。暂时只能解决到这个程度； ...
android studio出现no jdk specified for module怎么办？
01-19 2万+
如图， 右击模块->选择Open Module Settings->将Modules列表里各个Module的Properties中的Source Compatibility跟Target Compatibility的值清空。
Error:java: JDK isn‘t specified for module ‘xxx‘异常的解决方法
qq_53205631的博客
11-17 1万+
启动的项目的时候出现了一个这样的异常
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
05-08
WARNING: Unknown module: ALL-UNNAMED specified to --enable-native-access ``` #### 2. 解决方案 ##### 方法一：运行时添加JVM参数 在启动命令中明确启用本地访问： ```bash java --enable-native-access=ALL-...
WARNING: A restricted method in java.lang.System has been called WARNING: java.lang.System::load has been called by org.fusesource.jansi.internal.JansiLoader in an unnamed module (file:/D:/Environment/apache-maven-3.8.8/lib/jansi-2.4.0.jar) WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module WARNING: Restricted methods will be blocked in a future release unless native access is enabled WARNING: A terminally deprecated method in sun.misc.Unsafe has been called WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper (file:/D:/Environment/apache-maven-3.8.8/lib/guava-25.1-android.jar) WARNING: Please consider reporting this to the maintainers of class com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.046 s [INFO] Finished at: 2025-06-13T09:32:08+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [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/NoGoalSpecifiedException
06-14
2.restrictedmethodsun.misc.Unsafe的警告这个警告通常与使用旧版JDK（如JDK8）中的`sun.misc.Unsafe`类有关。在新版JDK中，这个类被视为受限API，不推荐使用。一些第三方库（如Netty、Guava等）可能使用了这个类，...
Starting Gradle Daemon... Gradle Daemon started in 14 s 275 ms > Task :prepareKotlinBuildScriptModel UP-TO-DATE Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01 Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01 Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01 Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/03 to old ns http://schemas.android.com/sdk/android/repo/addon2/01 Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01 Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/03 to old ns http://schemas.android.com/sdk/android/repo/repository2/01 Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/03 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01 Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01 Warning: 意外的元素 (uri:"", local:"base-extension")。所需元素为<{}codename>,<{}layoutlib>,<{}api-level>
07-17
- `Namespace not specified` 错误 - `Unexpected element 'base-extension'` 异常（通常由插件版本冲突引起） #### 解决方案 1. **声明模块命名空间** 在模块级 `build.gradle` 中添加： ```groovy android { ...
PS D:\Android\skin2> ./gradlew build --info WARNING: A restricted method in java.lang.System has been called WARNING: java.lang.System::load has been called by net.rubygrapefruit.platform.internal.NativeLibraryLoader in an unnamed module (file:/C:/Users/86177/.gradle/wrapper/dists/gradle-8.13-bin/5xuhj0ry160q40clulazy9h7d/gradle-8.13/lib/native-platform-0.22-milestone-28.jar) WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module WARNING: Restricted methods will be blocked in a future release unless native access is enabled Initialized native services in: C:\Users\86177\.gradle\native Initialized jansi services in: C:\Users\86177\.gradle\native Found daemon DaemonInfo{pid=25984, address=[98f52f11-5422-4822-a531-517066b0e039 port:43222, addresses:[/127.0.0.1]], state=Idle, lastBusy=1761229107209, context=Defaul tDaemonContext[uid=05f9d51e-3dfa-44e0-b71f-69781af5ef3b,javaHome=D:\Program Files\Android\Android Studio\jbr,javaVersion=21,javaVendor=JetBrains s.r.o.,daemonRegistryDi r=C:\Users\86177\.gradle\daemon,pid=25984,idleTimeout=10800000,priority=NORMAL,applyInstrumentationAgent=true,nativeServicesMode=ENABLED,daemonOpts=-Xmx2048m,-Dfile.encoding=UTF-8,-Duser.country=CN,-Duser.language=zh,-Duser.variant]} however its context does not match the desired criteria. JVM is incompatible. Wanted: DaemonRequestContext{jvmCriteria=D:\Program Files\Java\jdk-24 (no JDK specified, using current Java home), daemonOpts=[-Xmx2048m, -Dfile.encoding=UTF-8, -Duser.country=CN, -Duser.language=zh, -Duser.variant], applyInstrumentationAgent=true, nativeServicesMode=ENABLED, priority=NORMAL} Actual: DefaultDaemonContext[uid=05f9d51e-3dfa-44e0-b71f-69781af5ef3b,javaHome=D:\Program Files\Android\Android Studio\jbr,javaVersion=21,javaVendor=JetBrains s.r.o.,da emonRegistryDir=C:\Users\86177\.gradle\daemon,pid=25984,idleTimeout=10800000,priority=NORMAL,applyInstrumentationAgent=true,nativeServicesMode=ENABLED,daemonOpts=-Xmx2048m,-Dfile.encoding=UTF-8,-Duser.country=CN,-Duser.language=zh,-Duser.variant] Looking for a different daemon... The client will now receive all logging from the daemon (pid: 39468). The daemon log file: C:\Users\86177\.gradle\daemon\8.13\daemon-39468.out.log Starting 4th build in daemon [uptime: 25 mins 44.983 secs, performance: 100%, GC rate: 0.00/s, heap usage: 0% of 2 GiB] Using 16 worker leases. Now considering [D:\Android\skin2] as hierarchies to watch Watching the file system is configured to be enabled if available File system watching is active Starting Build Settings evaluated using settings file 'D:\Android\skin2\settings.gradle.kts'. Projects loaded. Root project using build file 'D:\Android\skin2\build.gradle.kts'. Included projects: [root project 'skin', project ':app'] > Configure project : Evaluating root project 'skin' using build file 'D:\Android\skin2\build.gradle.kts'. Resolved plugin [id: 'com.android.application', version: '8.13.0', apply: false] > Configure project :app Evaluating project ':app' using build file 'D:\Android\skin2\app\build.gradle.kts'. Resolved plugin [id: 'com.android.application', version: '8.13.0'] Using default execution profile All projects evaluated. Task name matched 'build' Selected primary task 'build' from project : FAILURE: Build failed with an exception. * What went wrong: Could not determine the dependencies of task ':app:test'. > Could not create task ':app:testDebugUnitTest'. > Could not create task of type 'AndroidUnitTest'. > Could not create an instance of type org.gradle.api.internal.tasks.testing.DefaultTestTaskReports. > Could not create an instance of type org.gradle.api.reporting.internal.DefaultReportContainer. > Type T not present * Try: > Run with --stacktrace option to get the stack trace. > Run with --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. BUILD FAILED in 3s
最新发布
10-24
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module 以及关于Daemon的警告： JVM is incompatible. Wanted: ... jdk-24 ... Actual: ... jbr,javaVersion=21 ... 这...
no jdk specified
wuqingsen1的博客
10-09 8384
在用 IDEA 编写 Kotlin 代码时，遇到了一个问题： no jdk specified 翻译为没有指定 jdk ；如下图所示： 下面给出我自己解决的方法： 1.打开 File --&gt; Project Structure... --&gt; SDKs 添加一个 JDK 目录，完毕后点 OK 即可；如下图所示： 2.打开 File --&gt; Project Stru...
IDEA 启动项目报错 Error running ‘XXXApplication‘: No jdk for module ‘XXX‘
由入门到精通
10-13 2974
找到File>Project Structure…在Dependencies中添加JDK。点击Apply,OK即可。
idea Error:java: JDK isn‘t specified for module ‘XXXX‘
hj970321的博客
06-25 258
在idea右键项目，选择project structure，打开modules，选择dependencies 选择下方module sdk为java version就可。
导入的项目图标中显示的为J橘色标，而不是三角号的运行按钮，但在代码区可以右键运行并出现弹窗，光标移入Main class中有No JDK specified for module错误提示的解决方法
qq_58631598的博客
02-29 1399
3.点击Add Content Root，选择自己导入刚才运行不了的那个项目,点击OK，再点击外层窗口的 Apply,OK。4.随机选取一个爆红的词，悬浮其上方，出现一个小窗口，在小窗口中点击More actions。5.点击More actions后，继续点击下面的Setup SDK。6.点击Setup SDK后，选择对应的JDK版本。2.在项目结构中点击模块。
Error running ...: No jdk for module
weixin_42731498的博客
09-07 2万+
一、错误 Error running …: No jdk for module … Error running …: No jdk for module … 二、解决方法 找到File>Project Structure…>Modules。 可以看到右边“Source“目录下面为空。点击”+“号，选择自己的项目或者模块 把自己的项目或者模块添加进来 在Dependencies中添加JDK 点击Apply,OK即可 回到项目中，重新导入一下包即可。 ...
Error running...No JDK for module....
qq_63524016的博客
12-04 772
第一步 第二步：添加自己的项目模块 如果不为空则跳过这一步第三步：在Dependencies中添加JDK 然后点击Apply OK 即可
IDEA启动项目Error:java: JDK isn‘t specified for module的解决方法？
热门推荐
Do_LaLi的博客
08-05 2万+
IDEA启动项目Error:java: JDK isn't specified for module的原因是idea自带jdk有问题，配置成自己下载安装的jdk就可以了！
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值