java - Local jars are not included in class path -

I am trying to create my application using Maven and Eclipse. I have dependencies on 3rd party jars which are on my local machine. Here my pom.xml is

   & Lt; Version & gt; 0.4 & lt; / Edition & gt; & Lt; Scope & gt; System & lt; / Scope & gt; & Lt; SystemPath & gt; C: /gelcap/lib/zipdiff-0.4.jar< / SystemPath & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Log4j & lt; / Group & gt; & Lt; ArtifactId & gt; Log4j & lt; / ArtifactId> & Lt; Version & gt; 1.2.11 & lt; / Edition & gt; & Lt; / Dependencies & gt;  

When I run mvn: Install it creates a war file for my project but the problem is that it does not include the zipdiff.jar file in the web-inf / lib folder. It only includes files that are downloaded. I also need to include a copy of the file from my local system, but Maven ignores them. I have no idea why this is happening because my war file does not include files with system scope. Please give me an idea how this problem might be solved. Thanks in advance

With the scope of "system", the container is expected to provide artifacts. From:

Provided

This is very similar to the compilation, but it indicates that you have JDK or container reliance on runtime Expect to provide. For example, while creating a web application for Java Enterprise Edition, you will determine the reliability of the serlet API and related Java EE API for the claim because the web container provides those sections. This scope is available only on the compilation and testing class, and is not infected.

[...]

System

This is similar to providing the scope, except that you have to provide a jar In which this clearly artifact is always available and not seen in a repository.

Using the system scope, you are pointing to the war plug-ins that the container will provide this dependency, since it is not what you intend to do, the easiest solution is to You can put artifacts in the repository in your local Maven repository, or you can repo your own intake on your intranet.

The target can be used to install a file (without POM) in your local store. After doing this, change the dependency type to "Compile" and remove the "System Path" element.

In my day-to-day job, we use our intranet to manage company-wide stores. You can get different repositories for your own artworks, you can create third party artifacts. The Nexus also acts as a proxy, accelerating the caching artifacts from the external treasures, the fastest building. This means that only the developer who uses new dependencies is not available in other reps - after that, all other deities can use it - they can checkout with SCM and worry about the creation of reliance Can build without doing.