[ 
https://issues.apache.org/jira/browse/MRM-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Stockhammer closed MRM-1989.
-----------------------------------
    Resolution: Fixed

Archiva uses JPA in the current master branch for 3.0.0. Build with JDK 11 is 
part of our integration tests.

> Compatibility with Java 11 and WildFly 16
> -----------------------------------------
>
>                 Key: MRM-1989
>                 URL: https://issues.apache.org/jira/browse/MRM-1989
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 2.2.4
>            Reporter: Noël Vaes
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Deployment of Archiva 2.2.4 (WAR) works on WildFly 16 and JDK 8
> It fails on WildFly 16 and JDK11.
> This is the error from the WildFly log with JDK11:
> {{ERROR [JPOX.RDBMS.Schema] (ServerService Thread Pool -- 80) Failed 
> initialising database. Exception : The java type int (jdbc-type="", 
> sql-type="") cant be mapped for this datastore. No mapping is available.}}
> {{javax.jdo.JDOFatalException: The java type int (jdbc-type="", sql-type="") 
> cant be mapped for this datastore. No mapping is available.}}
>  
> Since Java 11 is an LTS-release it might be a good idea to provide 
> compatibility with Java 11 in the next major release.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to