We can overwrite this behavior by adding a few lines of code. That is why dependency management is a vital part of every software project. To raise new issues or bugs against Gradle, please use github.com/gradle/gradle/issues. * I am building a Kotlin + Java application using IntelliJ 2019.3.1 Community, on Windows 10 Pro, with Gradle. The build.gradle file provides the necessary libraries for the build, dependency management for the project classpath and war file, and the target settings for maven and deployment of the Building Block. We need two things to make it work: a Main-Class attribute in the manifest file; Include dependencies jars; Let's add few modifications to the Gradle task: attributes(" Main-Class ", " de.example.main.Application ")} // Or without the parentheses: jar manifest. See, with earlier versions, we only needed one dependency. I create a JAR artifacts using the "from modules with dependencies" option, where a path to META-INF\MANIFEST.MF is required (if it is left blank, IntelliJ seems to find a MANIFEST.MF from an extracted dependency package) Edit the build.gradle and bb-manifest.xml files build.gradle . Whenever I make a change which will affect MANIFEST.MF, I run "gradle overrideManifest" and wuff generates clean manifests which respect the Bundle-Activators that I put in. Merging manifest entries can be cumbersome. In JUnit 5, though, the API is separated from the runtime, meaning two dependencies. instruction ' Bundle-ActivationPolicy ', ' lazy ' Copy link Quote reply aalmiray commented Sep 17, 2014. This blog post describes how we can manage the dependencies of our projects with Gradle. Let's start with modifying the jar task from the Java Gradle plugin. By default, this task produces jars without any dependencies. We will learn to configure the used rep manifest. This is where we see a noteworthy difference between JUnit 5 and earlier versions. Append additional information from our info plugin to the info section of the ivy.xml Now that we've specified the platform, we need to supply the JUnit dependencies. It is challenging, if not impossible, to create real life applications which don’t have any external dependencies. In the example above, I think you're going to want to also add . These must be edited to reflect your project requirements.