Correct.

And since there is no actual parent project, I suspect that is completely fine.

I think I would probably add a parent pom as well, so I don't need to repeat so much in each sub project, and also to be able to compile all modules by issuing a single command.

i always have one myself

Yeah, if those modules are only used in that single project, a parent pom is always a good idea.

@thomasnield Let me know how my approach works for you!

@edvin thank you I will check!

@edvin if its an idea issue, Ill let JB know

I think they already know, I think I saw an issue for this a while back. That might have been Gradle only though, not sure.

@edvin looking at this now

@edvin it looks like this works now. But it also works without me doing the facets on my Galago... argh! Let me remote into my work machine and see if I can apply this solution to the original problem

@thomasnield OK, great. It's a small but annoying thing. Hopefully it will be fixed soon, but now we know how to work around it. Forgive me if I asked you about this earlier, but are the modules used from several projects or just one?

The parent project (the one with no dependencies, but others are dependent on) is used for several projects.

And thank you : )

Do you think the modular approach is better for that purpose?

@thomasnield Oh, I didn't mean app1, I meant the folder that contains both of them. OK, I understand what you're doing now, and I think the structure you have now should work just fine. I normally always install those projects in the local repo, so I have control over when I share changes with the dependent projects, but I think you're just working a little differently with this, and really - whatever works is good IMO 🙂

@edvin yeah my workflow is a bit unconventional, mostly because it is liberal about making changes to dependencies on-the-fly rather than planning release cycles of the dependencies.

And thank you again : )

@thomasnield I like that approach. You still modularize your code base and avoid entanglement but you don't need all the processes involved with releasing, so that seems like a good choice 👏

@edvin I feel validated now, I'm not crazy!

I'm sorry for the lack of action lately, I will investigate if I'm allowed to talk about that project I've mentioned and let you guys know 🙂

@thomasnield Haha 🙂

@edvin and I can understand why that approach doesn't work with most environments that require careful stability. Mine thrives in careful anarchy.

and no worries, but looking forward to what you're making either way!

It has also been good to take a little break and just enjoy the summer. I miss working on the project almost every day, and will be back stronger than ever after summer 🙂

FYI all on D3. Gaetan is the authority on charting in #datascience as he's trying to build a cross-platform charting library for Kotlin.

OK, so D3 is not the way to go according to him. If he's already working on a cross platform library maybe it's not the right move to put lots of effort into this, but I wonder which way he'll be leaning when it comes to visualization? Will he leverage JavaFX?

I didn’t spend time on it for the moment. I’m going to dig a little bit 😉

@gaetan Awesome, no rush! We are still just scouting out simple POC's. But please feel free to share if you whip up something interesting.