Initial Infrastructure setup doesn't work on a Windows machine
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- aws, java
- Domain
- cloud, infrastructure
Research direction
Start by opening cdk.json and tracing how infrastructure-setup.sh invokes it; compare the existing app command with the Windows-generated cdk init Java command. Verify that the chosen default works on Windows, macOS, and Linux and that infrastructure setup completes.
Written by the indexing model from the issue text.
Description
Running the infrastructure-setup.sh doesn't work on a Windows machine. The issue is with the cdk.json file and how the app is specified. Currently, it is set to:
./mvnw -e -q compile exec:java
This fails on Windows due to the forward slash.
If I run a brand new cdk init app --language=java on a Windows machine the cdk.json file is set to:
mvn -e -q compile exec:java
Propose updating the default to support Windows, Mac and Linux.
- Dominant language
- Java
- Stars
- 70
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Two open-case totals on one screen: the Programs tile says 15,858 and the nav badge says 15,868 Openbug frontend maui-pilot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100