[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin

[remp...@gmail.com (JIRA)]

Title: Message Title

Stefan Rempfer commented on JENKINS-53247   Re: Support JCasC in Config File Provider Plugin Currently the JCasC plugin couldn't used as optional dependency because of a Java7/ Java 8 clash: [INFO] --- maven-enforcer-plugin:1.4.1:enforce (display-info) @ config-file-provider --- [INFO] Restricted to JDK 1.7 yet io.jenkins:configuration-as-code:jar:1.0-rc2:compile contains io/jenkins/plugins/casc/CasCGlobalConfig.class targeted to JDK 1.8 [WARNING] Rule 2: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message: Found Banned Dependency: io.jenkins:configuration-as-code:jar:1.0-rc2 Use 'mvn dependency:tree' to locate the source of the banned dependencies. So only the setter for "org.jenkinsci.plugins.configfiles.GlobalConfigFiles.getConfigs()" could be added. The Configurator registration have to be done in JCasC plugin integration project. Oleg Nenashev: Would his be suitable for you, even this fits not 100% to the roadmap of JCasC plugin? Dominik Bartholdi: Is there a plan to baseline the plugin on Java 8? Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.