.WAR file produced in releases?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Under Assets there is a .war file:
https://github.com/OHDSI/WebAPI/releases/tag/v2.10.1
I'm unsure how this .war file is produced but it is confusing since users will download it with an expectation that it will work in their environment. Instead they should build the .war file so their local configuration will work: https://github.com/OHDSI/WebAPI/wiki/WebAPI-Installation-Guide#building-the-webapi-war-file-using-maven.
Should we remove this from GitHub? Alternatively, perhaps there is a way to inject the configuration into the .war that is produced by GitHub?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the v2.10.1 GitHub release and its attached .war asset, then review the WebAPI Installation Guide section on building the WAR with Maven. Determine whether the released artifact contains environment-specific configuration; done means establishing whether it should be removed, rebuilt, or accompanied by clear configuration guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100