Move CAS test suite data into separate artifact
Open
⚙️ Refactoring
- Dominant language
- Java
- Stars
- 71
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the refactoring action**
Currently, the CAS test suite data is part of `uimaj-core`. UIMA 3.3.0 shipped the `tests` artifact to Maven Central, but apparently 3.4.1 no longer does that.
**Expected benefit**
Having the CAS test suite data in a separate artifact removes the need to ship the `tests` artifact and makes the test suite more easily accessible by downstream projects like `uima-uimaj-io-jsoncas`.
Contributor guide
Research direction
Start by locating the CAS test suite data within uimaj-core and reviewing how the tests artifact is currently published to Maven Central. Done means the data is available in a separate artifact and downstream projects such as uima-uimaj-io-jsoncas no longer need the tests artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100