Springboot project structure

We have a set of rest apis that need to be implemented. The apis in turn interact with other partners. A Core module will have the controllers, core logic and interfaces and other modules will have partner specific implementations.

I have two completely opposite ways of doing it.

1. Partner Module as dependency to core - I am thinking of a multi module project structure like this. I can then build the core jar with spring-boot-maven plugin keeping the module/modules i want as dependencies to the core.

   parent pom
       |-----------Core module
       |-----------India Module
       |----------Africa Module
       |--------- Europe Module
   
   

2. Core as dependency to Partner Modules - But there are suggestions in the team to create core module as a separate project/jar and host it in nexus repo. That way new partners can just take that dependency and start implementing.

Which one would be better and why?