Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java Quarkus Devfile doesn't run in dev mode due to installed Maven being too old #1541

Open
datho7561 opened this issue May 9, 2024 · 1 comment · May be fixed by devfile/registry#399
Open
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working

Comments

@datho7561
Copy link

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area ci
/area api
/area library
/area registry
/area alizer
/area devworkspace
/area integration-tests
/area test-automation
/area releng
/area landing-page

What versions of software are you using?

Go project

Operating System and version:

Go Pkg Version:

Node.js project

Operating System and version:

Node.js version:

Yarn version:

Project.json:

Web browser

Operating System and version:

Browser name and version:

Bug Summary

Describe the bug:

To Reproduce:

  1. Create a project using odo and the Quarkus Devfile
  2. You will need a k8s cluster or podman installed for the next step. I used a kind cluster
  3. Try to run the project using odo dev
  4. It should mention a warning regarding port forwarding
  5. Open the logs (odo logs --follow) and see that there is a compilation error related to Maven being too old

Expected behavior

Devfile runs the Quarkus project

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Additional context

I discovered this bug in VS Code OpenShifot, but VS Code OpenShift just calls odo (v3).

Any workaround?

Modify the Devfile to use the maven wrapper included in the project files.

eg. mvn ==> ./mvnw

Suggestion on how to fix the bug

Perform the substitution from mvn to ./mvnw in the Devfile being served in the Devfile Registry.

@openshift-ci openshift-ci bot added kind/bug Something isn't working area/registry Devfile registry for stacks and infrastructure labels May 9, 2024
@Jdubrick
Copy link
Contributor

PR opened here that will close the issue: devfile/registry#399

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working
Projects
Status: Waiting
Development

Successfully merging a pull request may close this issue.

2 participants