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

Richard Eckart de Castilho commented on UIMA-6293:
--------------------------------------------------

In the UIMA SVN repo, there are multiple artifacts located under the 
{{https://svn.apache.org/repos/asf/uima/build}} location and they all share 
common trunk/tags/branches. In order to prepare a migration into split GitHub 
repos, I am going to move the artifacts around a bit. I.e. for the case of the 
parent POM:

* {{https://svn.apache.org/repos/asf/uima/build/trunk/parent-pom}} -> 
{{https://svn.apache.org/repos/asf/uima/build/parent-pom/trunk/}}
* {{https://svn.apache.org/repos/asf/uima/build/tags/parent-pom-*}} -> 
{{https://svn.apache.org/repos/asf/uima/build/parent-pom/tags/parent-pom-*}}
* 
{{https://svn.apache.org/repos/asf/uima/build/branches/UIMA-6185-Upgrade-parent-POM-plugins}}
 -> 
{{https://svn.apache.org/repos/asf/uima/build/parent-pom/branches/UIMA-6185-Upgrade-parent-POM-plugins}}

> Migrate UIMA Parent POM to GitHub
> ---------------------------------
>
>                 Key: UIMA-6293
>                 URL: https://issues.apache.org/jira/browse/UIMA-6293
>             Project: UIMA
>          Issue Type: Task
>          Components: Build, Packaging and Test
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Major
>
> There is a joint repo for all kinds of build artifacts on GitHub, but so far 
> it is only an SVN mirror (probably no longer updated). Also, instead of 
> having a repo with all the build stuff (which have independent release 
> cycles), it would be better to have one repo per artifact.
> * (x) Update GitHub repo
> * (x) Set SVN repo to read-only
> * (x) Add Jenkinsfile
> * (x) Update POMs svn -> git



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to