Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Debugger]Avoid need to modify pom.xml to support DataSonnet language
See original GitHub issuecurrently to evaluate expressions using DataSonnet in debugger, you need to add to the pom.xml:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-datasonnet-starter</artifactId>
</dependency>
<dependency>
<groupId>org.scala-lang</groupId>
<artifactId>scala-library</artifactId>
<version>2.13.3</version>
</dependency>
it is modifying the user project. it would be nice if these dependencies can be injected automatically when needed
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Issues · camel-tooling/camel-idea-plugin - GitHub
[Debugger]Avoid need to modify pom.xml to support DataSonnet language debugger enhancement. #646 opened on Dec 23, 2021 by apupier.
Read more >DataSonnet
DataSonnet extends JSonnet, a data-templating language designed for generating configuration files, used by businesses like Google and DataBricks. DataSonnet ...
Read more >DataSonnet - Apache Camel
Camel supports DataSonnet transformations to allow an Expression or Predicate to be used in the Java DSL or XML Configuration.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah we should actually go the other way. That languages shown in that “list” is only languages that are available in the running Camel application.
The intention is not that you can run any languages “as you wish” but use the languages that your Camel application are using.
Yeah I am adding JMX operations to the CamelContextMBean https://issues.apache.org/jira/browse/CAMEL-17383