gradle-plugin

I'm writing some gradle plugin and now I've faced with a problem that DriverManager doesn't see JDBC driver defined in buildscript dependency: I have next build.gradle file: buildscript { repositories { mavenCentral() } dependencies { classpath("com.h2database:h2:1.4.196") } } plugins { id "someplugin" } apply plugin: 'groovy' And when I invoke command defined in task that extends DefaultTask DriverManager.getConnection("jdbc:h2:mem:", "sa", "") I receive exception No suitable driver found for jdbc:h2:mem: There is no problem when I unit-test these classes - it happens only when I invoke

I work at a big company with a strict policy forbidding the unfiltered use of outside libraries. We have to pull everything from blessed corporate repositories, and not the bare internet, including gradle.org. Using gradle's original apply plugin syntax, in conjunction with a buildscript block, I can add (blessed) plugins to our repo and use them in builds. In other words: buildscript { repositories { maven { url "https://privaterepo.myemployer.com" } } dependencies { // various dependencies classpath "org.something:some-plugin:1.0" ... } apply plugin: "someplugin" Instead, I want to be able

I've got a simple project in Gradle 4.6 and would like to make an executable jar of it. I've tried shadow , gradle-fatjar-plugin , gradle-one-jar , spring-boot-gradle-plugin plugins but neither of them adds my dependencies declared as implementation (I don't have any compile ones). It works with compile e.g. for gradle-one-jar plugin but I would like to have implementation dependencies. Thank you very much! miskender You can use the following code. jar { manifest { attributes( 'Main-Class': 'com.package.YourClass' ) } from { configurations.runtimeClasspath.collect { it.isDirectory() ? it :

I have a lot of different flavors for my build that have specific resources and I don't want to clutter my src directory in my project with a bunch of flavor-specific directories, so I add the source sets from another folder in my project prior to the mergeResources task (mergeResources.doFirst). This has always worked for the past several versions of the Android Gradle plug-in (3.1.0-3.2.0 and some of the 3.3.0-alpha versions), but at a certain point, the 3.3.0-alpha AGP started causing build failures during this mergeResources task. Now I keep getting: BUILD FAILED in 35s 16 actionable tasks

I don't understand gradle plugins block apply plugin: 'someplugin1' apply plugin: 'maven' and other one: plugins { id 'org.hidetake.ssh' version '1.1.2' } In first block We have some plugin name. in second one package and version. I don't understand where I should use first block and when second one. The plugins block is the newer method of applying plugins, and they must be available in the Gradle plugin repository . The apply approach is the older, yet more flexible method of adding a plugin to your build. The new plugins method does not work in multi-project configurations ( subprojects ,

Getting this Warning (Even when variant.getAssemble() is not used anywhere): API 'variant.getAssemble()' is obsolete and has been replaced with 'variant.getAssembleProvider()'. I have updated following components: Android Studio v3.3 Gradle PlugIn v3.3 Gradle Distribution URL (gradle-wrapper.properties) distributionUrl=https\://services.gradle.org/distributions/gradle-4.10.1-all.zip gradle.properties android.debug.obsoleteApi=true variant.assemble has been deprecated and replaced by a new provider API. If for example you are using it as next: variant.outputs.all { output -> variant.assemble