[
https://issues.apache.org/jira/browse/CAMEL-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235476#comment-17235476
]
Aurélien Pupier edited comment on CAMEL-15860 at 11/19/20, 1:44 PM:
--------------------------------------------------------------------
might not be trivial. The logger was removed to avoid "classloader pain in
tooling" https://issues.apache.org/jira/browse/CAMEL-11239 in 2017, so in
Eclipse Desktop Fuse Tooling
On the other hand, Eclipse Fuse Desktop tooling is still on Camel 2.x and there
is still no plan to migrate yet
was (Author: apupier):
might not be trivial. The logger was removed to avoid "classloader pain in
tooling" https://issues.apache.org/jira/browse/CAMEL-11239 in 2017, so in
Eclipse Desktop Fuse Tooling
> Use a real logger instead of stdio for MavenVersionManger
> ---------------------------------------------------------
>
> Key: CAMEL-15860
> URL: https://issues.apache.org/jira/browse/CAMEL-15860
> Project: Camel
> Issue Type: Improvement
> Components: tooling
> Affects Versions: 3.6.0
> Reporter: Aurélien Pupier
> Priority: Major
> Fix For: 3.7.0
>
>
> org.apache.camel.catalog.maven.MavenVersionManager is providing a log boolean
> which allows to log caught exception (instead of swallowinf them)
> This is not working when using with Camel Language Server as the stdio is
> used for the communication of the Language Server Protocol.
> Using a real logger will allow to access these logs from Camel language
> Server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
