Generate project via Camel JBang
- Dominant language
- Go
- Stars
- 927
- Forks
- 387
- Avg merge
- 15h 5m
- Merged PRs (30d)
- 36
Description
### Requirement
As we are dropping the support of Camel K Runtime project, we need to establish an easy way to generate the maven project from source. The `camel export` should be the solution.
When this is enabled, we should consider the possible new features such as:
* Supports various runtime
* Possibility to rewrite the build pipeline and leverage a jbang/maven container instead of the same operator container (with `pod` strategy).
* Move building logic to Job instead of Pods
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin with the `camel export` entry point mentioned in the issue and determine how source should become a Maven project after Camel K Runtime support is dropped. Define what “done” means for runtime choices, the `pod` build strategy, and moving builds to Jobs; the issue names no files or tests, so the implementation path needs project-level investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- build-system, cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100