The system scope is deprecated and the issues you're running into is likely due to that. The solution is to add the library to your internal (remote) repo or at least your local repo.
/Anders On Mon, Oct 26, 2015 at 3:26 PM, reena upadhyay <[email protected]> wrote: > I want dependencies that are having system scope to be part of my project > final executable jar. I tried maven-assembly, maven-shade and > maven-dependency plugin. But using these plugins, only those dependency of > my project which were present in my local maven repository were getting > added. Dependency with system scope (not present in my local maven repo) > are not getting added in the final executable jar. > > I tried searching over google, but most of the links are suggesting to add > it local maven repo first. I have some limitations so I cannot add those > dependency on local repo. I want it to picked from file system directly, > and wanted it to be part of final executable jar. > > <!-- Teradta jdbc dependency --> > <dependency> > <groupId>org.teradata</groupId> > <artifactId>teradata</artifactId> > <version>4.0</version> > <scope>system</scope> > > <systemPath>${basedir}/../../../lib/terajdbc4.jar</systemPath></dependency> > > Above dependency is not getting added in the final jar that maven is > building. > > Please suggest me the right plugin with its usage for this use case. > > Any help on this would be really appreciated. >
