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

Add documentation about the camel plug-in in Che docs #14778

Closed
slemeur opened this issue Oct 4, 2019 · 2 comments
Closed

Add documentation about the camel plug-in in Che docs #14778

slemeur opened this issue Oct 4, 2019 · 2 comments
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@slemeur
Copy link
Contributor

slemeur commented Oct 4, 2019

Is your task related to a problem? Please describe.

As the Camel plugin has been integrated, having a dedicated documentation about how to use it in Che would be beneficial to the community.

There are already elements which have been written on the following blog post:
https://developers.redhat.com/blog/2019/05/21/apache-camel-development-on-eclipse-che-7/

@slemeur slemeur added kind/task Internal things, technical debt, and to-do tasks to be performed. area/doc Issues related to documentation labels Oct 4, 2019
@slemeur
Copy link
Contributor Author

slemeur commented Oct 4, 2019

Linking to: #12584

@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 Oct 4, 2019
@slemeur slemeur mentioned this issue Oct 4, 2019
23 tasks
@rhopp rhopp added severity/P2 Has a minor but important impact to the 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 Oct 4, 2019
@che-bot
Copy link
Contributor

che-bot commented Apr 1, 2020

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 Apr 1, 2020
@che-bot che-bot closed this as completed Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants