Otavio Rodolfo Piske created CAMEL-20265:
--------------------------------------------
Summary: camel-jbang: investigate moving to a separate sub-project
Key: CAMEL-20265
URL: https://issues.apache.org/jira/browse/CAMEL-20265
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Otavio Rodolfo Piske
As Camel JBang is receiving more and more attention from our community, it's
widely loved by the community and is seeing increased adoption.
As a result, we have been faced with many circumstances where it makes sense to
add features that are specific to the sub-projects. However, because Camel
JBang is a part of the Camel Core project, there are some risks and limitations
to what we can do.
Specifically:
* We have limited ability to reuse code from the sub-projects, because we
cannot introduce cyclic dependencies
* Our inability to reuse code, may lead to situations where the code is simply
copy/pasted, thus increasing the maintenance effort across the projects,
slowing down progress and decreasing the overall code/project quality.
* It slightly increases build and test time for the Camel Core project
* It makes contribution harder for beginners - as it is part of a much larger
project, that is harder to build and setup
* It decreases the cohesion of the Camel Core project
* It slows down the evolution of Camel JBang, as releasing it depends on
releasing a new Camel Core version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
