You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Simon Legner (Jira)" <ji...@apache.org> on 2020/06/03 19:40:00 UTC

[jira] [Commented] (JCS-204) Release JCS 3.0

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

Simon Legner commented on JCS-204:
----------------------------------

We've managed to complete the migration to {{package org.apache.commons.jcs3}} tracked in https://josm.openstreetmap.de/ticket/19208. Updating JOSM core was easy. Reaching out to 7 plugin maintainers and getting the affected plugins updated, took more effort.

> Release JCS 3.0
> ---------------
>
>                 Key: JCS-204
>                 URL: https://issues.apache.org/jira/browse/JCS-204
>             Project: Commons JCS
>          Issue Type: Task
>            Reporter: Simon Legner
>            Assignee: Thomas Vandahl
>            Priority: Major
>              Labels: release
>
> Many improvements have been made since the last 2.2.1 release in 2017: https://github.com/apache/commons-jcs/compare/commons-jcs-2.2.1...master
> [JOSM|https://josm.openstreetmap.de/] always has been using the latest SVN version of JCS without any known problems. We would like to switch to Apache Ivy for dependency management and thus require a published release.
> Can you craft a new 2.3 release of JCS? Are there any blockers?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)