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 (Closed) (JIRA)" <de...@uima.apache.org> on 2011/11/11 05:52:51 UTC

[jira] [Closed] (UIMA-1967) UIMAJ build from the top level

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

Marshall Schor closed UIMA-1967.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.0SDK
         Assignee: Marshall Schor
    
> UIMAJ build from the top level
> ------------------------------
>
>                 Key: UIMA-1967
>                 URL: https://issues.apache.org/jira/browse/UIMA-1967
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>    Affects Versions: 2.3.1
>            Reporter: Jukka Zitting
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.4.0SDK
>
>
> The uimaj 2.3.1 source release package is a bit misleading in that it places a copy of the uimaj/README file in the top level directory even though the advertised "mvn install" build command doesn't work from there.
> Instead of fixing that problem, it would seem like a good idea to actually move the uimaj/pom.xml and uimaj/README files directly to the top level directory in svn.
> As a potential further simplification, it seems to me like it would be possible to merge also the uimaj-distr/* and aggregate-uimaj/pom.xml files to the top level.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira