cas 6.2 Incompatible because this component declares an API of a component compatible with Java 11

cas 6.2 Incompatible because this component declares an API of a component compatible with Java 11

最近用到cas6.2的项目  配置基本按下面的来 其中配置jdk什么的都是百度的

https://blog.csdn.net/qq_40297844/article/details/106437993

但是导包出现国外的倒不进去  翻墙都没得用 最后从ali仓库一个一个捞出来的

就是在gradle.build里面加了一下代码 ,据我了解这应该是按顺序执行找不到会执行下一个

    maven { url 'http://maven.aliyun.com/nexus/content/groups/public/' }
    maven { url 'http://maven.aliyun.com/repository/gradle-plugin/' }
    maven { url 'http://maven.aliyun.com/repository/jcenter/' }
    maven { url 'http://maven.aliyun.com/repository/central/' }
    maven { url 'http://maven.aliyun.com/repository/google/' }

位置cas 6.2 Incompatible because this component declares an API of a component compatible with Java 11

cas 6.2 Incompatible because this component declares an API of a component compatible with Java 11

因为上面地址是国外的 我就不要了注释掉了  各位看官请执行调整

找包的话请看

https://blog.csdn.net/oTianKongLan123/article/details/107161648

还有下一步执行到gradlew.bat clean build 时候又出现问题  也就是当前主题了

* Where:
Build file 'F:\cas-overlay-template-6.2.1\build.gradle' line: 76

* What went wrong:
A problem occurred evaluating root project 'cas'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.apereo.cas:cas-server-core-api-configuration-model:6.2.0.
     Required by:
         unspecified:unspecified:unspecified
      > No matching variant of org.apereo.cas:cas-server-core-api-configuration-model:6.2.0 was found. The consumer was configured to find a runtime of a component compatible with Java 8, packaged as a jar, and its dependencies decl
ared externally but:
          - Variant 'apiElements' capability org.apereo.cas:cas-server-core-api-configuration-model:6.2.0 declares a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
          - Variant 'runtimeElements' capability org.apereo.cas:cas-server-core-api-configuration-model:6.2.0 declares a runtime of a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
   > Could not resolve org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0.
     Required by:
         unspecified:unspecified:unspecified
      > No matching variant of org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0 was found. The consumer was configured to find a runtime of a component compatible with Java 8, packaged as a jar, and its depende
ncies declared externally but:
          - Variant 'apiElements' capability org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0 declares a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
          - Variant 'runtimeElements' capability org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0 declares a runtime of a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 987ms

F:\cas-overlay-template-6.2.1>gradlew.bat clean build

FAILURE: Build failed with an exception.

* Where:
Build file 'F:\cas-overlay-template-6.2.1\build.gradle' line: 76

* What went wrong:
A problem occurred evaluating root project 'cas'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.apereo.cas:cas-server-core-api-configuration-model:6.2.0.
     Required by:
         unspecified:unspecified:unspecified
      > No matching variant of org.apereo.cas:cas-server-core-api-configuration-model:6.2.0 was found. The consumer was configured to find a runtime of a component compatible with Java 8, packaged as a jar, and its dependencies decl
ared externally but:
          - Variant 'apiElements' capability org.apereo.cas:cas-server-core-api-configuration-model:6.2.0 declares a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
          - Variant 'runtimeElements' capability org.apereo.cas:cas-server-core-api-configuration-model:6.2.0 declares a runtime of a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
   > Could not resolve org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0.
     Required by:
         unspecified:unspecified:unspecified
      > No matching variant of org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0 was found. The consumer was configured to find a runtime of a component compatible with Java 8, packaged as a jar, and its depende
ncies declared externally but:
          - Variant 'apiElements' capability org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0 declares a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
          - Variant 'runtimeElements' capability org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0 declares a runtime of a component, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.4/userguide/command_line_interface.html#sec:command_line_warnings

提示jdk版本不匹配 我就很奇怪 刚开始我就配置了open_jdk  在setting和 projectstructure中   还有环境变量  应该是没问题的啊

后面仔细一看 gradle.bat这个命令  在cas6.2.0根目录下。  里面有9个JAVA_HOME    由于我之前的项目要用到jdk1.8 所以我找了个可以兼容的方法  创建了个JAVA_HOME_OPEN  在path里进行切换  结果这边读取的还是JAVA_HOME 所以出问题  我就把里面的 JAVA_HOME全改成JAVA_HOME_OPEN 就开始下一步了

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请联系我们举报,一经查实,本站将立刻删除。

发布者:全栈程序员-站长,转载请注明出处:https://javaforall.net/2202.html原文链接:https://javaforall.net

(2)
全栈程序员-站长的头像全栈程序员-站长


相关推荐

  • 创建和调用动态链接库方法

    创建和调用动态链接库方法

    2021年9月3日
    50
  • vue slot插槽_笔记本内存条插槽显示4个

    vue slot插槽_笔记本内存条插槽显示4个为什么使用slotslot(插槽)在生活中很多地方都有插槽,电脑usb的插槽,插板当中的电源插槽插槽的目的是为了让我们原来的设备具备更多的扩展性比如电脑的USB我们可以插入U盘,手机,鼠标,键

    2022年7月29日
    6
  • 小程序onShow

    小程序onShow/***生命周期函数–监听页面加载*/onLoad:function(options){letthat=this;constopenid=app.globalData.openid||Storage.get().openid;initNoPage(this,[{api:”getPerson”,inData:{op…

    2022年6月16日
    51
  • spdlog 日志库学习,简易封装

    spdlog 日志库学习,简易封装spdlogwiki:https://github.com/gabime/spdlog/wiki别人的学习笔记:https://www.cnblogs.com/oucsheep/p/8426548.html别人的学习笔记:https://github.com/gabime/spdlog/wiki百度搜spdlog封装可以看到很多写的差不多的单例类,我看公司遗留的代码也是借鉴这些写的。最常见的是一开头就写上:#ifdef_WIN32#define__FILENAME__(s

    2022年6月23日
    57
  • IOC控制反转的三种方式

    IOC控制反转的三种方式这里写自定义目录标题IOC控制反转三种方式(1).在介绍之前,来了解一下注入的概念:IoC(控制反转)即依赖注入,就是指程序在运行过程中,如果需要另外一个对象协助完成时,无需在代码中创建被调用者,而是依赖外部的注入获取。Spring的依赖注入对调用者几乎没有任何要求,完全支持对象之间的依赖关系的管理。(2).依赖注入通常有两种方式:设置注入、构造注入和属性注入—设置注入:设置注入是通过s…

    2022年6月17日
    25
  • 建立access数据库的两种方法_e4a上传数据到数据库

    建立access数据库的两种方法_e4a上传数据到数据库本章内容 ◆数据库的设计概念与创建数据库。◆表的创建及表与表之间的关系。◆数据库的修改、设计与编辑。  一、数据库的设计 1.概念及准则 下面介绍数据库设计的概念,及由此而产生的数据库设计准则。Access2003数据库是所有相关对象的集合,包括表、查询、窗体、报表、宏、模块、Web页等。每一个对象都是数据库的一个组成部分,其中,表是数据库的

    2022年9月13日
    0

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

关注全栈程序员社区公众号