unable to compile to a 1.8 target jdk on https://jenkins.ci.cloudbees.com

[gmon...@redhat.com]

Since the last successful build I attempted in early March 2016, I am now getting compile failures
for jobs on https://jenkins.ci.cloudbee.com saying that 1.8 is an invalid target:

invalid target release: 1.8

and 

javac: invalid target release: 1.8

The compile snippet from my pom.xml was originally:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <source>1.8</source>
          <target>1.8</target>
        </configuration>
      </plugin>


I'm currently sitting at:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.5.1</version>
        <configuration>
          <source>1.8</source>
          <target>1.8</target>
          <compilerArgs>
            <arg>-verbose</arg>
          </compilerArgs>
        </configuration>
      </plugin>


Was there a recently imposed restriction I missed, or perhaps an update to maven on the system
that has broken something?

thanks for any help,
Gabe

[Michael Neale]

what is the plugin name that it is building (or trying to build)? 

[Arnaud Héritier]

Hi,

  I imagine you are talking about this one :

https://github.com/openshift/jenkins-plugin

https://jenkins.ci.cloudbees.com/job/plugins/job/openshift-pipeline-plugin/

  It is normal that it fails because the job is configured to use a JDK 7

  We can configure it to use J8 but if you are targeting J8 you have to remember that current versions of Jenkins core are always compatible with J7 and thus you'll lost all users running on this version (Jenkins core was compatible with J6 few months ago).

 The worst is that we don't have any system in the update center to inform about the java requirement thus users running on J7 will be able to install it and the plugin will die in fire when it will try to start with the classical "Unsupported major.minor version 52.0"

Cheers

  

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7802010e-04db-4a9f-a5cf-04cb8d8256aa%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

-----

Arnaud Héritier

http://aheritier.net

Mail/GTalk: aheritier AT gmail DOT com

Twitter/Skype : aheritier

[gmon...@redhat.com]

Yes that is the plugin I'm talking about.

While we understand / appreciate the J7 compliance angle, and it is something we are tracking (just not prioritizing, at least yeast), for now we
want the job configured for JDK 8.  Is posting the request here sufficient to make that happen, or is there an additional process I need to initiate?

thanks,
gabe

[Arnaud Héritier]

No problem. I reconfigured it.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ca22c2c3-c252-40e9-9f7e-bb8265aab880%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[gmon...@redhat.com]

Thanks Arnaud !