uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] Commented: (UIMA-1967) UIMAJ build from the top level
Date Thu, 16 Dec 2010 20:41:02 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972203#action_12972203
] 

Marshall Schor commented on UIMA-1967:
--------------------------------------

After some more thought and discussion, I think having 2 poms is confusing.  So, I'm now leaning
toward moving the current uimaj project pom up one level in the SVN tree, and therefore, also
in the default checkout tree.  Developers who find having that project show subfolders I guess
can "get used to it", or close the project if they're not working on it.

> 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
>            Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message