You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2010/09/04 12:07:32 UTC

[jira] Created: (UIMA-1862) upgrade docbkx plugin to 2.0.11

upgrade docbkx plugin to 2.0.11
-------------------------------

                 Key: UIMA-1862
                 URL: https://issues.apache.org/jira/browse/UIMA-1862
             Project: UIMA
          Issue Type: Improvement
            Reporter: Marshall Schor
            Assignee: Marshall Schor
             Fix For: build-parent-pom-docbook-3


upgrade parent-pom-docbook to use docbkx version 2.0.11 which fixes a problem we were working around by having a custom patch that all users needed to do in a one-time setup.

Fix one-time setup documentation to remove this custom patch.

update poms that depend on this to the new release level.

release using a similar multi-staging-repos release process as was done in this previous release note: http://markmail.org/message/4ae7zb4ucmivlkaa

add doc section to the site release.xml describing the multi-staging-repos approach for build tooling.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (UIMA-1862) upgrade docbkx plugin to 2.0.11

Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.

     [ https://issues.apache.org/jira/browse/UIMA-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor closed UIMA-1862.
--------------------------------

    Resolution: Fixed

> upgrade docbkx plugin to 2.0.11
> -------------------------------
>
>                 Key: UIMA-1862
>                 URL: https://issues.apache.org/jira/browse/UIMA-1862
>             Project: UIMA
>          Issue Type: Improvement
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: build-parent-pom-docbook-3
>
>
> upgrade parent-pom-docbook to use docbkx version 2.0.11 which fixes a problem we were working around by having a custom patch that all users needed to do in a one-time setup.
> Fix one-time setup documentation to remove this custom patch.
> update poms that depend on this to the new release level.
> release using a similar multi-staging-repos release process as was done in this previous release note: http://markmail.org/message/4ae7zb4ucmivlkaa
> add doc section to the site release.xml describing the multi-staging-repos approach for build tooling.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.