Krystian Panek

ok ;)

https://code.google.com/archive/p/jarjar/

this is because when some build script user will use AEM Plugin and other Plugin simultenously, then Gradle will negotatiate/ choose more recent version from these two which could not...

try removing dependency to commons IO / e.g `IOUtils.toString` replace with Kotlin extension function `InputStream.readText()` / or buffering version `input.bufferedReader().use { it.readText() }`

``` sh gradlew dependencies --configuration=implementation > Task :dependencies ------------------------------------------------------------ Root project - Gradle AEM Plugin ------------------------------------------------------------ implementation - Implementation only dependencies for compilation 'main' (target (jvm)). (n) +--- unspecified (n)...

e.g needed to avoid ``` dependencies { "implementation"("com.cognifide.gradle:aem-plugin:9.2.1") constraints { "implementation"("com.google.guava:guava:23.0") { because("version from gradle-aem-plugin breaks robot framework") } } ``` as of guava is very often incompatible between each...

org.reflections to be removed as of it uses old guava / 15.

guava removed by removing reflections, jackrabbit removed by removing vault and oakpal dependencies in 13.0.0; TODO: - remove commons-io and commons-lang3 - jarjar: pebble, sshd, jcifs/smb

the issue is more about the verbosity of progress indicator to do not hide important messages when they are available and build run even without `-i`

```kotlin aem.sync { userManager { val user = createUser("foo") { // User / UserOptions (id mandatory so it is method arg password = "custompassword" // if not specified , strong...