Hi everybody, i've an issue with maven repository, my situation is: ->

Project A

->

Module B

->

Dependency C

->

Maven Repo D

My

Module B

depends on

Dependency C

wich is stored in

Maven Repo D

. If i remove

Maven Repo D

from build gradle within

Project A

, gradle says that can't resolve

Dependecy C

(but I've added

Maven Repo D

within

Module B

). Is it clear enough? 😄 Any ideas?

what's a module in this context? a subproject?

Yes it's a sub project

I had an issue recently where my sub-module also contained a repo that was necessary to resolve a dependency. So, do you still have the necessary repos in all the modules?

@paccman ☝️

In a previous project I was able to use the application plugin - I can't seem to do that anymore using the latest intellij and kotlin plugin

@gildor commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: What is you problem with application plugin?

@gildor commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: BTW explicit application of java plugin is not necessary, Kotlin jvm plugin does this implicitly already Also, you don't need to apply Kotlin plugin in apply block, Kotlin plugin already applied in plugins block

@carolos commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: application doesn't have code completion and gradle won't build I get "Could not open cache directory"

@gildor commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: Check logs, there is should be some real error

@carolos commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: Expression 'application' cannot be invoked as a function.

@gildor commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: Probably because you try to apply junit plugin, but I don't see it in plugins block

@carolos commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9NJFSC69/application_plugin.txt: Unresolved reference: mainClassName

@carolos what about junit plugin?

here is my full build.gradle.kts @gildor

@gildor commented on @carolos’s file https://kotlinlang.slack.com/files/U82UG39B5/F9MU8QNDP/full_build_gradle_kts.kt: Strange, everything looks fine. And If you remove application plugin configuration everything works?

should IntelliJ use 4.6 by default?

Maybe I'm missing something... To resolve the dependency, used just in sub-module, I had to add its repository to project's Gradle file. I thought that there was a merge of all repositories from project and sub-modules... I have to study better these configurations.

FYI, we have an issue that prevent us to support Gradle Kotlin DSL and more generally

plugins { }

block on start.spring.io: https://github.com/gradle/gradle/issues/3902. See also https://github.com/spring-io/initializr/issues/334#issuecomment-372610859 and feel free to send feedbacks and ideas.

Is there a way to show autocomplete in groovy build script for custom gradle plugin extensions written in Kotlin?

Is it possible to provide different

gradle.properties

to gradle wrapper via command line?

This is a little off topic kotlin-wise, but when you have project “A” which pulls dependencies from say, maven central and bintray, and then you use project “A” as a dependency in project “B”. Does project “B” have to know that project “A” has transient dependencies in two different repositories, requiring me to and include both of those repositories in project “B”’s configuration? tl/dr; does the maven pom of a project include repository information for transient dependencies?

Does project “B” have to know that project “A” has transient dependencies in two different repositories, requiring me to and include both of those repositories in project “B”’s configuration?

i do believe that project B depends on A, then B needs to also be able to resolve those dependencies so will also need a repository. can fairly easily be tested by removing repositories in project B and having project B depend on A. Gradle may handle the "exposed" elements of project A (like the

api

configuration) so it does not need all the dependencies

does the maven pom of a project include repository information for transient dependencies?

i think that's a different question, and from my experience the answer is no (definitely for OSS, and havent seen it in any work ive done). published POMs generally dont contain the references as to where to get their transitive dependencies, just the declarations of those dependencies

Thanks @mkobit. I think I didn’t state the first part of my question clearly. But your answer to the second part covered it 👍

So, if I have a library with dependencies in both bintray and maven central; then consumers of said library as a dependency will have to include both bintray and maven central as repositories.

yup

or, wherever they can retrieve those dependencies (e.g. an internal proxy to maven central)

The situation illustrated from @christopher is similar to what i've tried to describe. So thanks @christopher and @mkobit i've understood that i must add the repositories used in sub-module also into my project.

It seems that the

apply

in the external script works, but the class

org.sonarqube.gradle.SonarQubeExtension

can't be found.