Details

    • Type: Improvement Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6.1
    • Fix Version/s: 1.6.1
    • Component/s: build
    • Labels:
      None

      Description

      Upgrade the JSword jars to the latest and greatest.

        Activity

        Hide
        DM Smith added a comment -

        I've upgraded the following:
        commons-codec-1.3 to commons-codec-1.4
        commons-net-1.4.1 to commons-net-2.2 (requires Java 5)
        commons-httpclient-1.3 to httpcomponents (httpclient-1.4-beta1 and httpcore-1.4) (both require Java 5)

        What's left:
        lucene-2.9.1 -> lucene-3.0.2 (requires Java 5)
        icu4j-4.0 -> icu4j-4.4.2 (implements Unicode 5.2 and requires Java 5)
        xalan-2.7.0 -> xalan-2.7.1
        xerces-j-2.7.1 -> xerces-j-2.11.0

        These last 3 are currently optional. If they are present, then JSword will run better (icu4j) and/or faster (xalan/xerces).

        Show
        DM Smith added a comment - I've upgraded the following: commons-codec-1.3 to commons-codec-1.4 commons-net-1.4.1 to commons-net-2.2 (requires Java 5) commons-httpclient-1.3 to httpcomponents (httpclient-1.4-beta1 and httpcore-1.4) (both require Java 5) What's left: lucene-2.9.1 -> lucene-3.0.2 (requires Java 5) icu4j-4.0 -> icu4j-4.4.2 (implements Unicode 5.2 and requires Java 5) xalan-2.7.0 -> xalan-2.7.1 xerces-j-2.7.1 -> xerces-j-2.11.0 These last 3 are currently optional. If they are present, then JSword will run better (icu4j) and/or faster (xalan/xerces).
        Hide
        DM Smith added a comment -

        All are updated now. Minor changes to Lucene indexers have been made. Note: if user is upgrading from Java 1.4.2 to Java 5 (or 6), some indexes will need to be recreated. This is because Java's version of Unicode has changed. Most users will have been using Java 5+ anyway. Only those on MacOSX Panther don't have Java 5+.

        Show
        DM Smith added a comment - All are updated now. Minor changes to Lucene indexers have been made. Note: if user is upgrading from Java 1.4.2 to Java 5 (or 6), some indexes will need to be recreated. This is because Java's version of Unicode has changed. Most users will have been using Java 5+ anyway. Only those on MacOSX Panther don't have Java 5+.
        Hide
        DM Smith added a comment -

        Lucene 3.0.2 is giving Android problems. 3.0.3 does not call the offending class.
        ICU 4.6 has just been released.

        Show
        DM Smith added a comment - Lucene 3.0.2 is giving Android problems. 3.0.3 does not call the offending class. ICU 4.6 has just been released.
        Hide
        DM Smith added a comment -

        Upgraded to Lucene 3.0.3 and icu4j 4.6.

        Show
        DM Smith added a comment - Upgraded to Lucene 3.0.3 and icu4j 4.6.
        Hide
        Chris Burrell added a comment -

        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.

        Show
        Chris Burrell added a comment - 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.
        Hide
        DM Smith added a comment -

        At this time, Maven is another way to build and do deployment of JSword and BibleDesktop. Ant will remain, "the" way.

        If it were clear to me how to update the pom files, I'd do it. I looked for the dependencies of the 3-rd party jars but did not find them.

        That said, someone needs to re-open this issue and submit a patch for the poms.

        Show
        DM Smith added a comment - At this time, Maven is another way to build and do deployment of JSword and BibleDesktop. Ant will remain, "the" way. If it were clear to me how to update the pom files, I'd do it. I looked for the dependencies of the 3-rd party jars but did not find them. That said, someone needs to re-open this issue and submit a patch for the poms.
        Hide
        DM Smith added a comment -

        Troy has suggested using Ivy with Ant. It looks like a good way to marry Maven and Ant. It connects to Maven2 repositories to grab dependencies.

        This would allow us to get the 3-rd party jars without storing them within the JSword project.

        Show
        DM Smith added a comment - Troy has suggested using Ivy with Ant. It looks like a good way to marry Maven and Ant. It connects to Maven2 repositories to grab dependencies. This would allow us to get the 3-rd party jars without storing them within the JSword project.

          People

          • Assignee:
            DM Smith
            Reporter:
            DM Smith
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: