Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Whenever an internal sub-module is added as a dependency the scope has to be set to provided.
If the scope is not mentioned it falls back to default scope which is compile, this makes the dependency jar (sub-module jar) to be copied to share/..../lib directory while packaging. Since we use copyifnotexists logic, the binary jar of the actual sub-module will not be copied. This will result in the jar being placed in the wrong location inside the distribution.