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

Use mvn commands to run and debug for java-maven-based devfiles #20791

Closed
apupier opened this issue Nov 18, 2021 · 3 comments
Closed

Use mvn commands to run and debug for java-maven-based devfiles #20791

apupier opened this issue Nov 18, 2021 · 3 comments
Labels
area/devfile-registry area/samples kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@apupier
Copy link
Contributor

apupier commented Nov 18, 2021

Is your enhancement related to a problem? Please describe

Currently, most devfiles are using java -jar target/*.jar.

the inconvenient of using java -jar is that it requires users to have launch the build task beforehand, and every time there si a modification done.
https://github.com/eclipse-che/che-devfile-registry/blob/884b521459fcc1b6657b2241044ccf222fd149c2/devfiles/java-web-spring/devfile.yaml#L59

Describe the solution you'd like

For instance to launch in debug with mvn with springboot

https://github.com/eclipse-che/che-devfile-registry/blob/884b521459fcc1b6657b2241044ccf222fd149c2/devfiles/apache-camel-springboot/devfile.yaml#L72

Describe alternatives you've considered

No response

Additional context

/!\ devfiles are currently in migration to devfile v2 in che-samples repository

@apupier apupier added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 18, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 18, 2021
@themr0c themr0c added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 19, 2021
@che-bot
Copy link
Contributor

che-bot commented May 20, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2022
@che-bot che-bot closed this as completed May 27, 2022
@svor svor reopened this Jul 19, 2022
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2022
@svor svor mentioned this issue Jul 19, 2022
51 tasks
@vitaliy-guliy
Copy link
Contributor

Devfile registry contains only five java maven based samples.
Two of them, that were using java -jar have been updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-registry area/samples kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants