Draft Create Auto Detect pom.xml file during Java detection

Open
#223 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, java
Domain
cli, tooling

Research direction

Start by tracing the Java detection flow used by draft create and how it chooses the Maven or Gradle prompt. Use the apps/java-maven/ sample and its pom.xml as the verification case; done means Draft detects Maven from the repository without prompting for the build tool.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.

When running draft create on the following folder https://github.com/buildpacks/samples/blob/main/apps/java-maven/, draft shows the following prompt:

[Draft] --- Detecting Language ---
Use the arrow keys to navigate: ↓ ↑ → ←
? Linguist detected Java, are you using maven or gradle?:
    gradle
  > maven

Mention what platform you want to support the new feature

OSS draft

Describe the solution you'd like

Draft should detect that maven is being used by seeing the pom.xml file in the repository.

Describe alternatives you've considered

There may be a better way to detect maven.

Additional context

(none)

Dominant language
Go
Stars
644
Forks
74
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 Azure/draft

All issues in Azure/draft

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.