[api/suggestion] rename pulumi mvn/gradle bootstrap properties
Open
Nobody has claimed this yet.
api/suggestion
area/build
impact/breaking
kind/enhancement
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
I was trying to embed pulumi into an existing spring boot project's pom.xml and I think it would be better to have all of the hardcoded properties that we're using prefixed with pulumi for easy adoption and to avoid clashes.
Affected area/feature
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
Inspect pkg/cmd/pulumi-language-jvm/main.go at lines 500-505 and 514-518, starting with the hardcoded Maven and Gradle bootstrap properties. Rename the properties with a pulumi prefix consistently so they can be used in an existing Spring Boot pom.xml without clashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100