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/06/23 22:07:51 UTC

[jira] Closed: (UIMA-1759) make project versioning more conventional

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

Marshall Schor closed UIMA-1759.
--------------------------------

    Resolution: Fixed

> make project versioning more conventional
> -----------------------------------------
>
>                 Key: UIMA-1759
>                 URL: https://issues.apache.org/jira/browse/UIMA-1759
>             Project: UIMA
>          Issue Type: Sub-task
>          Components: Build, Packaging and Test
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>
> 1) make aggregator poms distinct from parent poms
> 2) aggregator poms to specify which version(s) of modules they are including (some may not change release to release)
> 3) Eliminate the use of properties in values for versions  (these cause warning messages when used with maven 3 - saying this support will not work in the future)
> 4) align project versioning with the way the maven "release " plugin works.
> 5) make parent poms separately releasable, using the apache/maven convention for version numbering of these kinds of artifacts (e.g., simple number, starting with 1).

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