io-2.8.0.jar telegrambots-meta-5.0.1.1.jar failureaĬcess-1.0.1.jar listenablefuture-9999.0-empty-to-avoid-conflict-with-guĪva.jar jsr305-3.0.2.jar checker-qual-3.5.0.jar error_prone_annotationsĪs you can see, telegrambots-meta-5.0.1.1.jar is part of the classpath attribute.īy the way, I'm using Heroku Cloud to deploy this Mons-logging-1.2.jar commons-codec-1.11.jar httpmime-4.5.13.jar commons Jackson-2.32.jar jersey-entity-filtering-2.32.jar jersey-container-griz common-2.32.jar osgi-resource-locator-1.0.3.jar jakarta.activation-1.2 I understand that when working on Maven, there is a simple way to add classes on the classpath, and it's by adding the right dependency on the pom.xml file.Īnd I think it was successfully added on the classpath because this is what I get when I read the MANIFEST.MF file on my jar file: Manifest-Version: 1.0Ĭlass-Path: telegrambots-abilities-5.0.1.1.jar commons-lang3-3.11.jar ma After a little investigation, I found that is an error that occurs when a jar file is not able to access a specific class in runtime, and in order to solve this, is necessary to add that class on classpath. In this case, this is just a simply telegram bot, but I get this error when trying to run it locally. I'm trying to deploy my first java application using Maven.
0 Comments
Leave a Reply. |