@ron Good to hear from you by the way, I was about to send out an APB!

Not anymore Google completely switched for Android

I guess that makes sense to keep quality high. What's good about that is that they have to make sure the IDEA plugin works perfectly for them.

@edvin yeah, I like to clone dependency projects physically neighboring my main one, and have them all in the same workspace.

Ah, so you don't want to pull them from the maven repo, but from a neighboring folder instead?

@edvin exactly. It keeps my work fast and tactical without relying on dependency release cycles, although that has to be managed to some degree. I may post a SO question to see how it's done.

I will give it a quick shot, hang on.

@edvin you don't have to, but that would be awesome!

Thank you

On the phone 🙂

@edvin me too, no rush : )

I'll be at a computer soon if you do manage to find something

@thomasnield Do you need to rely on sources from that other project or do you want to package the dependency explicitly for it to show up?

It'd be great for it to show up so I can edit any of the projects within the same workspace.

OK

@thomasnield Last question. Can it be a multi module project, so they have a common root only shared by these modules?

@thomasnield Scratch that last. I got it 🙂

@User uploaded a file: app2 depending on sources from app1

I didn't include jvmTarget, source/target definitions etc for brevity.

@edvin cool! Let me try this right now....

Had it working then I broke something. One sec...

Brilliant! It works!

Thanks @edvin! I'm going to upload this example on GitHub for my reference as well as to help others.

@thomasnield Cool :))

I'm going to migrate my projects to this setup. In my workplace, the less setup, the easier it is to sell. Thanks this was super helpful

In Maven there is often one good way of doing things, but in Gradle I come across so many ways of expressing the same thing. Maybe it's just because I don't understand it, but it feels confusing for a beginner.

@edvin I came to that conclusion too. I am more than able to use Gradle, but as I start teaching Kotlin at work and at OReilly, the Gradle setup might intimidate people right off the bat. If you tell them all you need is JDK and Intellij, that is much easier to sell to beginners.

I'm glad I know Gradle but it doesn't have the works "right out of the box factor I value heavily

I hope things will improve. I think the internals of Gradle are more modern than Maven, but I do like type safety. Having to guess types when I write plugins is not my cup of tea, even if it's often much simpler to get the plugin to do what you want in Gradle. I was kind of amazed how little code was needed for the TornadoFX Gradle Plugin.

The base was written by Andres Almiray, and he really knows his stuff though.