[jira] [Commented] (SLING-11633) ClientSideTeleporter throwing illegal argument when target byte code is > 1.8

2024-02-12 Thread Sufyan Haroon (Jira)


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

Sufyan Haroon commented on SLING-11633:
---

Further changes are needed for running teleporter plugin with Java 11. Raised 
following PR

[https://github.com/apache/sling-org-apache-sling-junit-teleporter/pull/4]

Please review and merge. 

 

cc: [~bdelacretaz] 

> ClientSideTeleporter throwing illegal argument when target byte code is > 1.8
> -
>
> Key: SLING-11633
> URL: https://issues.apache.org/jira/browse/SLING-11633
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
> Environment: Apache Maven 3.8.5 
> (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> Maven home: C:\aem-tools\utils\apache-maven-3.8.5
> Java version: 11.0.15.1, vendor: Oracle Corporation, runtime: 
> C:\aem-tools\utils\jdk-11.0.15.1
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Scott Yuan
>Priority: Trivial
> Fix For: JUnit Tests Teleporter 1.0.24
>
> Attachments: mylab.zip
>
>   Original Estimate: 2h
>  Time Spent: 0.5h
>  Remaining Estimate: 1.5h
>
> When attempted to use the latest 1.0.22 to build test cases using 
> TeleporterRule with Java 11+ code, illegal arguments error occurred. 
> It can be reproduce with the attached Maven project by change following 
> properites to 11. 
> * maven.compiler.source
> * maven.compiler.target



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (SLING-11633) ClientSideTeleporter throwing illegal argument when target byte code is > 1.8

2022-10-24 Thread Scott Yuan (Jira)


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

Scott Yuan commented on SLING-11633:


After tracing throw the source code, upgrade the maven-dependency-anlayzer to 
the latest version solve the issue.  A single line pull request has been made 
in hope to help a bit.  
https://github.com/apache/sling-org-apache-sling-junit-teleporter/pull/2/commits/cd853a28682cf54926828153d3312b8f6035b05a

> ClientSideTeleporter throwing illegal argument when target byte code is > 1.8
> -
>
> Key: SLING-11633
> URL: https://issues.apache.org/jira/browse/SLING-11633
> Project: Sling
>  Issue Type: Improvement
>  Components: Apache Sling Testing Rules
> Environment: Apache Maven 3.8.5 
> (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> Maven home: C:\aem-tools\utils\apache-maven-3.8.5
> Java version: 11.0.15.1, vendor: Oracle Corporation, runtime: 
> C:\aem-tools\utils\jdk-11.0.15.1
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Scott Yuan
>Priority: Trivial
> Attachments: mylab.zip
>
>   Original Estimate: 2h
>  Time Spent: 20m
>  Remaining Estimate: 1h 40m
>
> When attempted to use the latest 1.0.22 to build test cases using 
> TeleporterRule with Java 11+ code, illegal arguments error occurred. 
> It can be reproduce with the attached Maven project by change following 
> properites to 11. 
> * maven.compiler.source
> * maven.compiler.target



--
This message was sent by Atlassian Jira
(v8.20.10#820010)