Hi , a question on two ways of adding implementati...

# gradle

[Razak]

Hi , a question on two ways of adding implementation dependencies

1. implemention "artifact detail's"
2.implemention project("project name")
Are they same? End of the day their in classpath in same way?
are their advantages of defining with project ?
*Considering include build multi modules project structure

[trevjones]

they should resolve the same but I would only use the project(":projectPath") when the project lives in the same repo. Otherwise the maven coordinates will be a better fit even when pulling in the project as a composite build.

with a composite build if you have your group and name of the projects matching it will auto substitute for you without any extra work.

[tapchicoma]

consider project(..) is a dependency on artifact produced by a project. So not much difference, it only the source from where artifact is loaded from:
• 1 -> from network (cache on disk)
• 2 -> from disk after project has finished assembling it

[Razak]

Oh then then their is no advantage of using one over the other , I saw idea/gradle automatically converts one defined using 1st way to 2nd even in case of composite builds within same repo...I was worried if it has impact on incremental build performance which is import for big repo in idea.