【IDEA】报错:Cannot access central (https://repo.maven.apache.org/maven2) in offline mode

1.报错描述:Cannot access central (https://repo.maven.apache.org/maven2) in offline mode

在这里插入图片描述

2.解决方案:Maven在离线模式下载不了jar包,点击以下按钮,打开在线模式即可,然后点击刷新按钮

在这里插入图片描述
补充同类型报错:

报错描述:

Could not transfer artifact org.apache.kafka:kafka-metadata:jar:3.0.2 from/to central (https://repo.maven.apache.org/maven2): Connection reset
在这里插入图片描述

解决方案:

pom.xml文件中导入依赖时不会自动下载依赖包,打开IDEA勾选以下选项
在这里插入图片描述

Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/maven-release-plugin-2.5.3.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/maven-release-plugin-2.5.3.pom (11 kB at 1.0 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/release/maven-release/2.5.3/maven-release-2.5.3.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/release/maven-release/2.5.3/maven-release-2.5.3.pom (5.0 kB at 502 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/27/maven-parent-27.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/27/maven-parent-27.pom (41 kB at 3.7 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/apache/17/apache-17.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/apache/17/apache-17.pom (16 kB at 1.5 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/maven-release-plugin-2.5.3.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/maven-release-plugin-2.5.3.jar (53 kB at 4.1 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml (14 kB at 1.3 MB/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21 kB at 764 kB/s) [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.954 s [INFO] Finished at: 2025-07-09T06:18:06Z [INFO] ------------------------------------------------------------------------ [ERROR] No plugin found for prefix 'spring-boot' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/root/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [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/NoPluginFoundForPrefixException root@srv771551:~/jeecg-boot# cd ../jeecgboot-vue3 -bash: cd: ../jeecgboot-vue3: No such file or directory root@srv771551:~/jeecg-boot# npm install npm run dev npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /root/jeecg-boot/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/root/jeecg-boot/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2025-07-09T06_18_32_236Z-debug-0.log npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /root/jeecg-boot/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/root/jeecg-boot/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2025-07-09T06_18_34_357Z-debug-0.log root@srv771551:~/jeecg-boot#
07-10
### 加快从 Gradle 插件仓库下载 Kotlin 依赖的方法 为了提高从 Gradle 插件仓库下载 Kotlin 相关依赖的速度,可以通过以下方式优化配置: #### 配置本地镜像源 通过设置 Maven 中央仓库的国内镜像地址来替代默认的 `http://repo.maven.apache.org/maven2` 地址。例如,阿里云提供了稳定的 Maven 镜像服务,可以在项目的 `build.gradle` 或全局的 `init.gradle` 文件中指定镜像源。 ```groovy repositories { maven { url "https://maven.aliyun.com/repository/public" } } ``` 此操作会将所有的 Maven 请求重定向到阿里云的镜像服务器上,从而显著提升下载速度[^5]。 #### 使用离线模式开发 如果团队内部已经存在所需的依赖项,则可以启用 Gradle 的离线模式以减少网络请求的时间消耗。在命令行执行构建任务时加上参数 `-offline` 即可激活该功能;或者是在 IDE 设置中勾选对应选项完成相同效果。 对于初次加载全部依赖的情况不建议开启此项特性,因为这可能导致某些新版本库无法被及时获取到[^1]。 #### 更新 Gradle 和插件至最新稳定版 保持使用的工具链处于最新状态有助于获得更好的性能表现以及修复已知问题的能力。比如升级到更高版本号如 '1.8.21' 可能带来兼容性和效率上的改进[^4]: ```groovy plugins { id 'org.jetbrains.kotlin.jvm' version '1.8.21' } ``` 同时也要注意配套使用的 Gradle 版本是否满足最低要求说明文档中的规定[^2]。 #### 并发下载多个文件 调整 JVM 启动参数允许更多线程参与资源抓取过程也能有效缩短整体耗时时长。修改 gradlew 脚本里的 JAVA_OPTS 环境变量定义部分增加如下内容: ```bash export GRADLE_OPTS="-Dorg.gradle.parallel=true -Xmx2g -XX:+UseG1GC" ``` 上述指令启用了并行计算机制(-parallel),分配给进程更大的堆内存空间(Xmx2g), 还采用了 G1 垃圾回收算法(UseG1GC)[^3]. --- ### 总结 综合运用以上策略能够很大程度缓解因公网带宽瓶颈所引发的低效现象。当然具体实施还需依据实际场景灵活变通处理。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值