reckart opened a new issue, #422:
URL: https://github.com/apache/uima-uimaj/issues/422
**Describe the refactoring action**
Exclude the `marker-file-enabling-auto-staging` from the source distribution.
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`.
**Expected benefit**
When currently building from the source ZIP, we get this problem:
```
[INFO] Apache UIMA Aggregate: aggregate-uimaj ............. SUCCESS [ 0.157
s]
[INFO] Apache UIMA Java SDK: uimaj ........................ FAILURE [ 16.576
s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 34:10 min
[INFO] Finished at: 2024-11-21T08:04:36-08:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:buildnumber-maven-plugin:3.2.1:create (generate-candidate-id)
on project uimaj: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command.: The git log command failed:
/bin/sh -c cd '/vol/secure/local/uima/test/uimaj-3.6.0' && 'git' 'log' '-1'
'--no-merges' '--format=format:%H %aI %aE %aN' returned fatal: not a git
repository (or any parent up to mount point /vol)
[ERROR] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not
set).
[ERROR] -> [Help 1]
```
This is due the auto-staging function:
https://nightlies.apache.org/uima/draft-guides/maint.html#_auto_staging_of_release_candidates
By excluding the marker files, people that build from the source ZIP will
not run into this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
