Hi Pablo, thanks for testing!
I think the issue already might have come up earlier but I forgot to address it. So to make releases more comfortable, UIMA will prepare a local staging area where it puts the release artifacts. During an actual release, these artifacts are then also pushed to the staging spot in the ASF SVN. But the preparation happens also during normal builds. For the release manager, this function is very very convenient. However, doing things in Maven is sometimes complicated and I have not found a good way to prevent the preparation of the staging area in non-release builds. For the function to work, Subversion needs to be set up locally. And also it seems that the buildnumber-maven-plugin does not fail gracefully when it is not in a git repo. There is actually a piece of documentation on this auto-staging here: https://nightlies.apache.org/uima/draft-guides/maint.html#_auto_staging_of_release_candidates Now to the issue at hand. I see three options: 1) try to change the build setup to somehow do it better automatically, in particular limiting the execution of the auto-staging stuff to release builds. As I said... tricky... not sure how to do it 2) Building with `-Ddisable-rc-auto-staging` - that should make your build complete. 3) Exclude the `marker-file-enabling-auto-staging` from the source distribution. Not sure if we can easily do that - but if we can, then a person building from the source ZIP we distribute would not have auto-staging. But... GitHub also creates a convenience source ZIP which could be downloaded from its release page. It seems we might also be able to exclude files from that one using the `export-ignore` feature of `.gitattributes`. I'll have a look at 3). Meanwhile you could see if 2) works for you. Cheers, -- Richard
