TelegramBots | Java library to create bots using Telegram Bots API | Bot library

Sounds like you want and need to create a runnable/ executable JAR file (with external dependencies).

This requires your build process to be enhanced by this step, regardless of where it is executed Heroku, Jenkins, Bamboo or on your local - this is a maven setting and will affect each of them.

Also on your local you can run the build of your project by executing mvn clean package in your IDE and afterwards to run the created JAR from the target folder with: java -jar ${yourJarName}. It'll likely fail for the same reason.

This is, because Maven dependencies are added with a so called scope. These are for example:

• compile
• provided
• runtime
• test

Whereby compile is the default one and being implicitly applied in case you don't specify it - like in your case. (You can read more about the scopes here)

This means Maven will add your dependency to your IDE at compile time, but it will be missing at the runtime, when your trying to execute it.

The solution is to create a runnable/ executable JAR file (also called *fat JAR *) containing all the needed dependencies.

You can do it directly within Maven with the help of the maven-assembly-plugin like so:

Use this code:

Check in your environment that the file was in utf-8u format Because Cyrillic may not be supported

Roughly speaking, you have two options

1. Make a "fat" JAR with all required classes present
2. Make a "thin" JAR that references other JAR files

What is most suitable for your situation is something only you can decide. Here's how you do it:

To follow this approach, you use the Maven Shade Plugin. In the package phase, you would invoke its shade goal. That would copy classes from your dependencies as well as your application classes together into one JAR-file. It could look like this in the POM:

it looks like the Maven Compiler plugin is using Java 5 (it should be using Java 6 by default), hence you get the build error diamond operator is not supported in -source 1.5

Heroku supports various Java version (see Supported Java versions), you should just be able to set the target version in your POM file

If your are using windows operating system, please use below command to call the jar file directly, no need to use tLibraryLoad component. This component can be used in case you are accessing any method from the jar. If you just want to execute the jar you can use below,

See the documentation.

Starting with version 2.1, type information can be conveyed in record Headers, allowing the handling of multiple types. In addition, the serializer/deserializer can be configured using Kafka properties.

JsonSerializer.ADD_TYPE_INFO_HEADERS (default true); set to false to disable this feature on the JsonSerializer (sets the addTypeInfo property).

JsonDeserializer.KEY_DEFAULT_TYPE; fallback type for deserialization of keys if no header information is present.

JsonDeserializer.VALUE_DEFAULT_TYPE; fallback type for deserialization of values if no header information is present.

JsonDeserializer.TRUSTED_PACKAGES (default java.util, java.lang); comma-delimited list of package patterns allowed for deserialization; * means deserialize all.

By default, the serializer will add type information to the headers.

see the boot documentation.

Similarly, you can disable the JsonSerializer default behavior of sending type information in headers:

spring.kafka.producer.value-serializer=org.springframework.kafka.support.serializer.JsonSerializer spring.kafka.producer.properties.spring.json.add.type.headers=false

Or you can add type mapping to the inbound message converter to map the source type to the destination type.

EDIT

Having said that, what version are you using?

I got it. The solution was kind of obvious. All you need is just use tor proxy:

There seem to be a few issues here

First

3.6.0 is not the Mongo driver library that was actually loaded into your application classpath; I suspect that you were previously testing with an old version, and recently updated the POM? You were previously using version 3.2.0.

How do I know this?

I started digging through the code, and at version 3.6.0, the error message you provided is nowhere near line 203. And also, you can see that the above linked code has support for the +srv.

Browing back through previousl releases, I finally found that error massge on line 203, back at release 3.2.0.

Long story short, trying doing a Maven clean, and rebuild.

Relaunch Eclipse to pick up new dependencies if a project refresh does not help.

Second

MongoTimeoutException: Timed out after 30000 ms while waiting for a server

This one is highly likely a firewall / access control group configuration issue, in that the firewall is blocking the packets from reaching your Atlas cluster.

See adding addresses to the whitelist.