Code generation

Open
#1,109 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java

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.

Description

ai-triaged bug reliability

Protobuf - Gradle

Protobuf - Maven - Manually run mvn protobuf:compile

Need configure source paths

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

Annotation Process - Maven

Manual step require:

Dominant language
TypeScript
Stars
352
Forks
166
Avg merge
17h 47m
Merged PRs (30d)
32

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-pack

All issues in microsoft/vscode-java-pack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.