Develop Reference

How to include shadows when publishing to Artifactory? (Gradle)

So for a little context: I have recently set up an Artifactory repository and I am new to working with Artifactory, everything I have been doing thus far has been from their user guide.
Now for the question: I would like to deploy a master plugin to Artifactory, but have it also include the shadowed dependencies on this using Gradle.
I have a general idea of deploying, and I have done so before, though I do not know how to deploy the code with the shadowed dependencies included and I am looking for some guidance that will allow me to do this.
I have included the parts of build.gradle that I believe is relevant for this:
artifactory {
contextUrl = "${artifactory_contextUrl}"
publish {
repository {
repoKey = 'sunace'
username = [REDACTED]
password = "${artifactory_password}"
}
defaults {
publishConfigs('archives', 'published')
properties {
all 'fun.sunace.master:MasterController:1.?:*#*', key2: 'val2', key3: 'val3'
}
publishBuildInfo = true
publishArtifacts = true
publishPom = true
publishIvy = false
publishForkCount = 8
}
}
clientConfig.setIncludeEnvVars(true)
clientConfig.info.addEnvironmentProperty('time.published',new java.util.Date().toString())
clientConfig.info.setBuildName('MasterController')
clientConfig.info.setBuildNumber('' + new Random(System.currentTimeMillis()).nextInt(20000))
clientConfig.timeout = 600
resolve {
repository {
repoKey = 'gradle-dev'
username = [REDACTED]
password = "${artifactory_password}"
maven = true
}
}
}
If you need anything else, just ask and I will amend the post with the requested assets.
Thanks to all those who help!

Gradle - Syntax error using plugin method with closure as argument

Below are two tasks hello & printProperties in build.gradle:
task('hello', {
description("Hey student! Run this one :D")
group("Our demo")
doLast({println("Hello World!")})
}
)
plugins({
id('java')
})
ext({
springVersion = "3.1.0.RELEASE"
emailNotification = "build#master.org"
})
sourceSets.all({ ext.purpose = null })
sourceSets({
main({
purpose = "production"
})
test({
purpose = "test"
})
plugin({
purpose = "production"
})
})
task('printProperties', {
doLast({
println(springVersion)
println(emailNotification)
sourceSets.matching({ it.purpose == "production" }.each({ println it.name }))
})
})
that gives error:
> startup failed:
build file '/../../build.gradle': 8:
only buildscript {} and other plugins {} script blocks are allowed before plugins {} blocks, no other statements are allowed
Why plugins({id('java')}) give groovy scripted syntax error?

It's answered here : https://stackoverflow.com/a/48611069/1250435
Whenever you write a build.gradle script and use the new plugins
script block, you need to put it as first block in the file. The only
exceptions from this rule are other plugins blocks or the special
buildScript block, which always must go first.

Getting Play Framework works with Gradle and IntelliJ Idea

I'm trying to build my web application with Play Framework using Gradle as a build tool. My IDE is IntelliJ Idea.
I use Play with Java so I don't want to use SBT in my project. But it seems Play's not supported fully by IntelliJ Idea because the project structure is quite different. IntelliJ can't recognize it.
After a while googling, I found a solution, adding this script in build.gradle:
idea {
module {
sourceDirs += file("app")
testSourceDirs += file("test")
scopes.COMPILE = [plus: [configurations.play], minus: []]
scopes.RUNTIME = [plus: [configurations.playRun], minus:[configurations.play]]
scopes.TEST = [plus: [configurations.playTest], minus: [configurations.playRun]]
}
}
But there is a problem, each time I open the project, I have to re-run idea task to make IntelliJ recognize the Play's structure.
Is there any way that's better than mine?
Thank you so much!
My Github example: https://github.com/TranNgocKhoa/play-gradle-intellij-example.
My build.gradle
plugins {
id 'play'
id 'idea'
}
def playVersion = "2.6.7"
def scalaVersion = System.getProperty("scala.binary.version", /* default = */ "2.11")
model {
components {
play {
platform play: playVersion, scala: scalaVersion, java: '1.8'
injectedRoutesGenerator = true
sources {
twirlTemplates {
defaultImports = TwirlImports.JAVA
}
}
}
}
}
def dependencyFor(String lib, String scalaVersion, String version) {
return lib + "_" + scalaVersion + ":" + version
}
dependencies {
play dependencyFor("com.typesafe.play:play-guice", scalaVersion, playVersion)
play dependencyFor("com.typesafe.play:play-logback", scalaVersion, playVersion)
play dependencyFor("com.typesafe.play:filters-helpers", scalaVersion, playVersion)
play dependencyFor("com.typesafe.play:play-java-jpa", scalaVersion, playVersion)
play "org.hibernate:hibernate-core:5.4.2.Final"
play "com.h2database:h2:1.4.197"
}
repositories {
jcenter()
maven {
name "lightbend-maven-releases"
url "https://repo.lightbend.com/lightbend/maven-release"
}
ivy {
name "lightbend-ivy-release"
url "https://repo.lightbend.com/lightbend/ivy-releases"
layout "ivy"
}
}
idea {
module {
sourceDirs += file("app")
testSourceDirs += file("test")
scopes.COMPILE = [plus: [configurations.play], minus: []]
scopes.RUNTIME = [plus: [configurations.playRun], minus: [configurations.play]]
scopes.TEST = [plus: [configurations.playTest], minus: [configurations.playRun]]
}
}
I'm using Java 8, Gradle 5.4, Play 2.6.7

The below setup works now with some finessing required to get the rest of your dependencies up and running.
plugins {
id 'play'
id 'idea'
}
# replace with
plugins {
id 'idea'
id 'org.gradle.playframework' version '0.9'
}
The next step is to execute gradle idea and you should be able to just import the folder and intellij. If that is not the case go to Build tools -> Gradle and select use gradle

The use Gradle properties in build.gradle

I read through this, official Gradle reference and migration guide, and I still cannot figure out why the following build script doesn't work.
apply plugin: 'java-library'
repositories {
jcenter()
}
dependencies {
testImplementation group: 'org.testng', name: 'testng', version: '6.14.3'
}
def t_threads = test_threads
test {
useTestNG() {
setParallel('methods');
setThreadCount(t_threads)
}
maxParallelForks = t_threads
}
task printProps {
println test_threads
}
My gradle.properties file:
test_threads = 1
gradle printProps fails on the line setThreadCount(t_threads) with the exception: Could not find method setThreadCount() for arguments 1 on object of type org.gradle.api.tasks.testing.testng.TestNGOptions. If I change my code to def t_threads = 1, then gradle printProps finishes without an error displaying 1.

Answer is quite simple. setThreadCount expects Integer as a parameter, but property is a String, so all I had to do is convert String to Integer using test_threads as Integer.

init.gradle read properties from command line

In my gradle script I've been able to successfully read properties like this:
def environment = hasProperty('env') ? env : 'dev'
Using this I can execute a build script like this:
gradlew clean assemble -Penv=prod
My issue comes in when I tried moving this to an init.gradle file. The file is recognized and I'm able to use other properties that I define in the script, however I'm not able to get any from the command line. How can I do this?
My init.gradle file:
allprojects {
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'com.android.tools.build:gradle:0.6.+'
}
}
project.ext['nexusDomainName'] = 'https://example.com/nexus'
project.ext['compileSdkVersion'] = 19
project.ext['buildToolsVersion'] = "19"
project.ext['minSdkVersion'] = 8
project.ext['targetSdkVersion'] = 19
project.ext['sourceCompatibility'] = '1.7'
project.ext['targetCompatibility'] = '1.7'
//hasProperty('release') is always false
project.ext['archiveType'] = hasProperty('release') ? '' : '-SNAPSHOT'
project.ext['archiveUrl'] = hasProperty('release') ? "$nexusDomainName/content/repositories/releases/" : "$nexusDomainName/content/repositories/snapshots/"
// This buildEnv property won't read either
project.ext['buildEnv'] = hasProperty('env') ? env : 'dev'
println "prepping for $buildEnv"
project.ext['archivesBaseNameSuffix'] = (project.ext['buildEnv'] == 'stage' || project.ext['buildEnv'] == 'dev') ? '-' + project.ext['buildEnv'] : ''
repositories {
mavenLocal()
maven {
credentials {
username 'username'
password 'password'
}
url "$nexusDomainName/content/groups/public/"
}
mavenCentral()
}
}

-P sets a project property, which isn't immediately available in an init script. (You can access projects and their properties from an init script, but that access will be deferred until the projects have been created.) However, using a system property (-D) should work.