Re: [M2] runtime scope but not transitive

Mmmm, then, why do you want to stop transitivity? If you depend on a war module which depends on implJarModule at runtime, then your final module will also depend on it. Maybe your final module includes another implementation? Anyway, I guess what you need is to declare the dependency as:

Re: [M2] runtime scope but not transitive

Hi Rodrigo, Thanks for your reply, Mmmm, then, why do you want to stop transitivity? If you depend on a war module which depends on implJarModule at runtime, then your final module will also depend on it. Maybe your final module includes another implementation? It's not rely that I want to

Re: [M2] runtime scope but not transitive

I think provided is the right value for this Regards Rémy Sanlaville wrote: Anybody can help me (isn't it clear enough) ? any thoughts? Rémy -- --- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17

Re: [M2] runtime scope but not transitive

Thanks Rodrigo for your reply. I think provided is the right value for this I prefer to say provided is the best solution (compared with the others) but not the right. Why ? Because if you need my warModule, you will see that it has a dependency to implJarModule with the provided scope. So

[M2] runtime scope but not transitive

Hi, I would like to have your advice for this problem. Context: I have a multi-modules project : project | | earModule (depends on warModule, apiJarModule, implJarModule) | | warModule (depends on apiJar, apiJarModule, implJarModule, mockImplJarModule and spring) |