[jsword-devel] [JIRA] Commented: (JS-135) Upgrade 3-rd party jars

[Chris Burrell (JIRA)]

    [ http://www.crosswire.org/bugs/browse/JS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642#action_13642 ] 

Chris Burrell commented on JS-135:
----------------------------------

Had a brief look through the commits, but it seems the pom.xml files haven't changed (except for one in javancss). Is that something that got missed? Each pom has a dependencies and/or a dependency management section at the top which should be updated. 

Are we still maintaining several ways of building JSword? Would it make sense to move towards Maven given its portability and not the others... Don't know what developers use apart from that and whether it would cause issues just to have one way of building things.

> Upgrade 3-rd party jars
> -----------------------
>
>                 Key: JS-135
>                 URL: http://www.crosswire.org/bugs/browse/JS-135
>             Project: JSword
>          Issue Type: Improvement
>    Affects Versions: 1.6.1
>            Reporter: DM Smith
>            Assignee: DM Smith
>            Priority: Minor
>             Fix For: 1.6.1
>
>
> Upgrade the JSword jars to the latest and greatest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.crosswire.org/bugs/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira