Hi, those aren't really exclusions, it just means that e.g. uimafit has its own branches and tags. The standard setup is to mirror all branches and tags in git (and it's quite important if you want to work on some release branch, e.g.). They are not included as folders, branches and tags in git are metadata.

When mirroring SVN to git you need to tell it where to find the branches (including master, i.e. trunk) and tags, which is easy if your repository follows the standard SVN layout. The parts I mention are actually ignored by default, simply because uimafit, ruta, etc. are not branches of sandbox or anything of that kind, so they are not part of the standard SVN structure.

HTH,
Jens

On 11/19/2013 09:12 AM, Richard Eckart de Castilho wrote:
Is there any reason why do work with excludes on the sandbox and include
all svn management folders (tags, branches trunk) instead of just mirroring
trunk?

I'd somehow have a more cozy feeling without things being excluded.

-- Richard

On 18.11.2013, at 20:27, Richard Eckart de Castilho <[email protected]> wrote:

Could that be "uima-uimafit" or simply "uimafit"?

-- Richard

On 18.11.2013, at 17:08, Jens Grivolla <[email protected]> wrote:

Hello, if there are no objections, I will file a ticket for the following on 
INFRA:

We would like to have a git mirror of the Apache UIMA SVN. As the project has 
many submodules with individual trunk/branches/tags structure we would like the 
following mapping:

uimaj                   uima-core.git
uimacpp         uima-cpp.git
uima-as         uima-as.git (ignore uima-as/depend-on-parent-pom-4)
addons          uima-addons.git
sandbox         uima-sandbox.git (ignore sandbox/{ruta,uima-ducc,uimafit})
sandbox/ruta            uima-ruta.git
sandbox/uima-ducc       uima-ducc.git
sandbox/uimafit uima-fit
site                    uima-site
build                   uima-build (ignore build/archive)
ignore eclipse-packagings

All of these follow the standard SVN layout.

Comments?

Jens


On 11/15/2013 01:02 PM, Jens Grivolla wrote:
Ok, AFAICS due to the project structure we would actually need a
separate mirror for each sub-project (uimaj, uimacpp, uima-as,
uima-addons, uima-sandbox, ...)

Also, some sub-projects don't purely follow the trunk,tags,branches
structure, such as sandbox which additionally contains other
sub-projects (uimafit, ruta, ...) which have their own
trunk,tags,branches structure. These would probably need to have their
own independent mirrors outside of uima-sandbox.

I have no idea how to deal with eclipse-packagings, and uima-as has an
additional depend-on-parent-pom-4 at the top level that seems weird.

Any comments?

Jens

On 11/15/2013 12:50 PM, Jörn Kottmann wrote:
On 11/15/2013 12:20 PM, Jens Grivolla wrote:
Ok, so who can do it? Does it need to come from the PMC?


You can just go ahead and do it.

Jörn




Reply via email to