cqframework / cqframework/vscode-cql
0.7.7 - Hardcoded maven registry makes it un-installable in corporate VPNs where package mirrors are mandatory
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The maven location is hardcoded: https://github.com/cqframework/vscode-cql/blob/master/src/javaServiceInstaller.ts#L67 -- This does not work in many corporate VPNs where directly access to upstream registries is blocked and users must use local mirrors.
You will need to consider what a user may have in $HOME/.m2/settings.xml and/or $MAVEN_HOME/conf/settings.xml first, then fallback to the current hardcoded implementation.
Contributor guide
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 in src/javaServiceInstaller.ts at the hardcoded Maven location around line 67. Read how the installer currently chooses the registry, then investigate the two Maven settings.xml locations named in the issue and define the fallback behavior. Done means users behind mandatory corporate mirrors can install successfully while the current registry remains a fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100