[jira] [Resolved] (UIMA-5359) uv3 set up svn spot for uv3 and dependent projects

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

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

Marshall Schor resolved UIMA-5359.
----------------------------------
    Resolution: Fixed

> uv3 set up svn spot for uv3 and dependent projects
> --------------------------------------------------
>
>                 Key: UIMA-5359
>                 URL: https://issues.apache.org/jira/browse/UIMA-5359
>             Project: UIMA
>          Issue Type: Task
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 3.0.0SDK-beta
>
>
> UIMA v3 needs a more prominent spot in SVN.  Sub-projects that depend on uv3 need a spot too.  These need to co-exist with v2 UIMA, since migration is  something that will occur over time, and early versions are needed for testing.
> The current svn layout: https://svn.apache.org/repos/asf/uima.
> Under that we have 
> * addons  (trunk, tags, branches)
> * build (trunk, tags, branches)
> * eclipse-packagings (archive, not currently used?)
> * ruta (trunk, tags, branches)
> * sandbox (trunk, tags, branches)
> * site (trunk - this is the website)
> * uima-as (trunk, tags, branches, depend-on-parent-pom-4 (to-be-deleted))
> * uimacpp (trunk, tags, branches)
> * uima-ducc (trunk, tags, branches)
> * uimafit (trunk, tags, branches)
> * uimafit-v3 (trunk only)
> * uimaj (trunk, tags, branches)
> We could follow the convention started by uimafit, of adding a -v3 suffix. 
> We could put in a top level additional folder, say "uv3", and put exisiing projects which have a v3 migration, there. 
> I'm not sure which is better.  I suppose the additional high level folder would keep the number of subfolders in the top level smaller, so might be a good thing, so i'm leaning toward that.  
> Opinions?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)