You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@johnzon.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2018/02/26 12:48:00 UTC
[jira] [Commented] (JOHNZON-149) Release Johnzon 1.0.1
[ https://issues.apache.org/jira/browse/JOHNZON-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376806#comment-16376806 ]
Mark Struberg commented on JOHNZON-149:
---------------------------------------
Hi Alexandre!
Is there any reason you cannot use the 1.1.x branch?
Means are you bound to JSON-P 1.0? Or would JSON-P 1.1 and JSON-B 1.0 (EE8 level) be fine for you?
> Release Johnzon 1.0.1
> ----------------------
>
> Key: JOHNZON-149
> URL: https://issues.apache.org/jira/browse/JOHNZON-149
> Project: Johnzon
> Issue Type: Task
> Components: Core, Documentation, JAX-RS, JSON-B, Mapper, Websocket
> Affects Versions: 1.0.0
> Reporter: Alexandre Vermeerbergen
> Priority: Major
> Fix For: 1.0.1
>
>
> Hello,
> There hasn't been activity on 1.0.1 branch since JOHNZON-101 was fixed.
> We have several webapps to be migrated to TomEE+ 7 which are in regression without this fix.
> Would it be possible to release Johnzon-1.0.1 as soon as possible, with associated Maven artifacts, so that it will be possible to target it for TomEE 7.0.5?
> Best regards,
> Alexandre
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)