microsoft / microsoft/vscode-java-pack
Code generation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
Description
Protobuf - Gradle
- https://github.com/square/retrofit.git
- https://github.com/traccar/traccar.git
- https://github.com/MovingBlocks/Terasology.git
Protobuf - Maven - Manually run mvn protobuf:compile
- https://github.com/google/truth.git
- https://github.com/apache/hbase.git
- https://github.com/signalapp/Signal-Server.git
- https://github.com/hazelcast/hazelcast-jet.git
- https://github.com/alibaba/Sentinel.git
Need configure source paths
- https://github.com/javaparser/javaparser.git
- Sources will be generated after running
mvnw javacc:javacc, but it's not recognized into the source paths
- Sources will be generated after running
- https://github.com/eclipse/eclipse-collections.git
- Sources are generated after running
mvn clean install -DskipTests, but it's not recognized into the source paths. Workaround: manually set the m2e lifecycle mapping in pom.xml.
- Sources are generated after running
M2E lifecycle mapping - manual steps: find quickfix in pom.xml and set the m2e lifecycle mapping in pom.xml
Out of scope
Annotation Process - Gradle
- https://github.com/real-logic/simple-binary-encoding.git
- Need to run
./gradlew, and then reload projects.build/generated-srcwill be added to the source paths
- Need to run
- https://github.com/real-logic/agrona.git
- https://github.com/Discord4J/Discord4J.git
Annotation Process - Maven
Manual step require:
- https://github.com/protostuff/protostuff
mvn clean install && mvn eclipse:eclipse
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
Review the listed Gradle and Maven projects, starting with the generated-source and source-path cases described for javaparser, eclipse-collections, and the annotation-processing examples. Compare the current behavior after the stated Maven or Gradle commands, including the manual pom.xml lifecycle-mapping steps. Done means the relevant generated sources and configured source paths are recognized without the documented manual workarounds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100