Tine Kondo

Hi @mklueh I'm currently improving the support for multi-modules projects to accommodate this use case( Initial PR is here: https://github.com/tinesoft/nxrocks/pull/210) It should be fixed very shortly. So stay tuned! ;-)

Hi @algoflows Sorry for the delay in responding... I don't know enough KMP to answer just yet... I'll have to check and get back to you. Stay tuned

Hi @ToppScorer Thanks for using the plugin and for reporting this. Can you provide the following information, * **Output** of `nx report` * **Actual stacktrace** when running nx install [app-project]...

Hi, I was not aware of that **Maven CI friendly** versioning... But I did try to reproduce your setup (one app, one lib, app's `pom.xml` has a dependency on lib,...

> No, they are not connected, Ok that's your issue then! ^^ The setting to connect the `install` targets can be set either **globally** in the `nx.json` ( in the...

Can share the two `pom.xml ` and the two `project.json` files ?

Humm... That's very odd... there must be something else in your `pom.xml` that is messing the dependency detection system of the plugin. Only that section should matter: ```xml com.example example-lib...

Thanks for the repro project. I can see your problem now: You didn't create the app and library projects right: You created them as Maven **multi-module** projects _while using them...

Hi, > The example repo has a perfectly valid Maven setup. Yes you're right (bad wording from my part), taken individually, each of the project is indeed a valid Maven...

Hi @batnyu Thanks for using the plugin and for reporting this. The signature of `createNodesFor` method (from `common-jvm`) has changed in the latest version. But that should be transparent for...