[ 
https://issues.apache.org/jira/browse/SLING-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461997#comment-16461997
 ] 

Carsten Ziegeler commented on SLING-7644:
-----------------------------------------

As version 2.3.4 is mentioned in our parent pom, it's impossible to build our 
java 7 based modules with Java 7. 
So we have two options, either move back to 2.3.2 for our parent pom and 
declare that the maven sling plugin requires Java 8

or

fix this Java 8 dependency in 2.3.6 and change our parent pom to 2.3.6

But the way it is atm does not make that much sense.

> Maven-Sling-Plugin requires Java 8
> ----------------------------------
>
>                 Key: SLING-7644
>                 URL: https://issues.apache.org/jira/browse/SLING-7644
>             Project: Sling
>          Issue Type: Bug
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Maven Sling Plugin 2.3.4
>            Reporter: Carsten Ziegeler
>            Priority: Blocker
>             Fix For: Maven Sling Plugin 2.3.6
>
>
> When using the maven sling plugin 2.3.4 with Java 7, the following error 
> occurs:
> [ERROR] Failed to execute goal 
> org.apache.sling:maven-sling-plugin:2.3.4:generate-adapter-metadata 
> (generate-adapter-metadata) on project org.apache.sling.resourceresolver: 
> Execution generate-adapter-metadata of goal 
> org.apache.sling:maven-sling-plugin:2.3.4:generate-adapter-metadata failed: 
> An API incompatibility was encountered while executing 
> org.apache.sling:maven-sling-plugin:2.3.4:generate-adapter-metadata: 
> java.lang.UnsupportedClassVersionError: javax/json/JsonException : 
> Unsupported major.minor version 52.0
> [ERROR] -----------------------------------------------------
> [ERROR] realm =    plugin>org.apache.sling:maven-sling-plugin:2.3.4
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/Users/cziegeler/.m2/repository/org/apache/sling/maven-sling-plugin/2.3.4/maven-sling-plugin-2.3.4.jar
> [
> Reverting to version 2.3.2 fixes the problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to