Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.1SDK
    • Labels:
      None

      Description

      1) eliminate need for any individual project checkout to depend on another project being checked out simultaneously. This includes:

      • switching to docbkx maven plugin instead of our own docbook tooling (see other subtask)
      • using maven-remote-resources plugin for including common, shared things, rather than referring to other projects (see other subtask)
      • use POM dependencies from the repositories

      2) make POMs inherit from Apache master POM.

      3) separate parent poms from aggregation poms.

      4) make POMs inherit from Apache common POM

      5) make parent poms separately releasable, using the apache/maven convention for version numbering (single digit).

      6) position aggregator poms in the conventional position (not flat structure) to enable some plugins (assembly and release) to function better.

        Activity

        Hide
        Marshall Schor added a comment -

        Probably 99% of the fixup work has been finished, except that the aggregates are not "above" the projects they aggregate in the svn or working copy. I think maven might be able to make that work - many fixes recently in various plugins support this.

        1) docbkx - done, including olink support via maven repo
        using maven-remote-resource - done
        using POM dependencies from repo - done

        2) use master Apache POM - done (found 2 issues in Apache master POM - fixed in our top level pom)

        3) parent poms and aggregation poms separated

        4) same as 2

        5) parents and build tools separately releasable - done

        6) aggregator poms on top - ** not done, won't fix (for now) **

        7) Other work done:

        • remove DISCLAIMER files
        • remove most uses of incubator (left = some issues with namespaces)
        • cleaned up Javadoc warnings
        • created top level uima-wide POM with standard things
        • created single-project and pear-packaging parent poms
        • improved common NOTICE file template to allow sticking in additional required notices
        • fixed <url>, and fixed <scm> parts of all poms - required for release
        • moved rat processing so it runs on each project's sources, put required exclusions in each projects pom
        • cleanup properties use, follow maven 3 requirements
        • made next version 2.3.1-SNAPSHOT
        Show
        Marshall Schor added a comment - Probably 99% of the fixup work has been finished, except that the aggregates are not "above" the projects they aggregate in the svn or working copy. I think maven might be able to make that work - many fixes recently in various plugins support this. 1) docbkx - done, including olink support via maven repo using maven-remote-resource - done using POM dependencies from repo - done 2) use master Apache POM - done (found 2 issues in Apache master POM - fixed in our top level pom) 3) parent poms and aggregation poms separated 4) same as 2 5) parents and build tools separately releasable - done 6) aggregator poms on top - ** not done, won't fix (for now) ** 7) Other work done: remove DISCLAIMER files remove most uses of incubator (left = some issues with namespaces) cleaned up Javadoc warnings created top level uima-wide POM with standard things created single-project and pear-packaging parent poms improved common NOTICE file template to allow sticking in additional required notices fixed <url>, and fixed <scm> parts of all poms - required for release moved rat processing so it runs on each project's sources, put required exclusions in each projects pom cleanup properties use, follow maven 3 requirements made next version 2.3.1-SNAPSHOT
        Hide
        Richard Eckart de Castilho added a comment -

        Reopening issue to reassign them from version 2.3.1 to 2.3.1SDK or 2.3.1Addons before removing version 2.3.1 from Jira.

        Show
        Richard Eckart de Castilho added a comment - Reopening issue to reassign them from version 2.3.1 to 2.3.1SDK or 2.3.1Addons before removing version 2.3.1 from Jira.
        Hide
        Richard Eckart de Castilho added a comment -

        Finishing transition from 2.3.1 to 2.3.1SDK

        Show
        Richard Eckart de Castilho added a comment - Finishing transition from 2.3.1 to 2.3.1SDK

          People

          • Assignee:
            Marshall Schor
            Reporter:
            Marshall Schor
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development