How to add local jar files to a Maven project

Question

How do I add local jar files  not yet part of the Maven repository  directly in my project s library sources

User · Answer

lt dependency gt       lt groupId gt group id name lt  groupId gt       lt artifactId gt artifact name lt  artifactId gt       lt version gt version number lt  version gt       lt scope gt system lt  scope gt       lt systemPath gt jar location lt  systemPath gt   lt  dependency gt

User · Answer

mvn install       You can write code below in command line or if you re using eclipse builtin maven right click on project -  Run As -  run configurations    -  in left panel right click on Maven Build -  new configuration -  write the code in Goals  amp  in base directory    project loc NameOfYourProject  -  Run    mvn install install-file    -Dfile  lt path-to-file gt     -DgroupId  lt group-id gt     -DartifactId  lt artifact-id gt     -Dversion  lt version gt     -Dpackaging  lt packaging gt     -DgeneratePom true   Where each refers to    lt  path-to-file    the path to the file to load e g -  c  kaptcha-2 3 jar   lt  group-id    the group that the file should be registered under e g -  com google code   lt  artifact-id    the artifact name for the file e g -  kaptcha   lt  version    the version of the file e g -  2 3   lt  packaging    the packaging of the file e g  -  jar     2 After installed  just declares jar in pom xml      lt dependency gt         lt groupId gt com google code lt  groupId gt         lt artifactId gt kaptcha lt  artifactId gt         lt version gt 2 3 lt  version gt    lt  dependency gt

User · Answer

Create a local Maven repository directory  Your project root should look something like this to start with    yourproject  - pom xml  - src    Add a standard Maven repository directory called repo for the group com example and version 1 0    yourproject  - pom xml  - src  - repo    Deploy the Artifact Into the Repo  Maven can deploy the artifact for you using the mvn deploy deploy-file goal    mvn deploy deploy-file -Durl file    pathtoyour repo -Dfile your jar -DgroupId your group id -DartifactId yourid -Dpackaging jar -Dversion 1 0    install pom file corresponding to your jar so that your project can find jar during maven build from local repo    mvn install install-file -Dfile  path-to-your-jar-1 0 jar -DpomFile  path-to-your-pom-1 0 pom    add repo in your pom file     lt repositories gt       lt  --other repositories if any-- gt       lt repository gt           lt id gt project local lt  id gt           lt name gt project lt  name gt           lt url gt file   project basedir  repo lt  url gt       lt  repository gt   lt  repositories gt     add the dependency in your pom     lt dependency gt       lt groupId gt com groupid lt  groupId gt       lt artifactId gt myid lt  artifactId gt       lt version gt 1 0 lt  version gt   lt  dependency gt

User · Answer

On your local repository you can install your jar by issuing the commands   mvn install install-file -Dfile  lt path-to-file gt  -DgroupId  lt group-id gt    -DartifactId  lt artifact-id gt  -Dversion  lt version gt  -Dpackaging  lt packaging gt    Follow this useful  link to do the same from mkyoung s website  You can also check maven guide for the same

User · Answer

I think a better solution for this problem is to use maven-install-plugin to automatically install the files at install time  This is how I set it up for my project    First  add the path  where you store the local  jars  as a property    lt properties gt       lt local sdk gt  path to jar lt  local sdk gt   lt  properties gt    Then  under plugins add a plugin to install the jars when compiling    lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-install-plugin lt  artifactId gt       lt version gt 2 5 2 lt  version gt       lt executions gt           lt execution gt               lt id gt 1 lt  id gt               lt phase gt initialize lt  phase gt               lt goals gt                   lt goal gt install-file lt  goal gt               lt  goals gt               lt configuration gt                   lt groupId gt com local jar lt  groupId gt                    lt artifactId gt appengine-api lt  artifactId gt                   lt version gt 1 0 lt  version gt                   lt packaging gt jar lt  packaging gt                   lt file gt   local sdk  lib impl appengine-api jar lt  file gt               lt  configuration gt           lt  execution gt           lt execution gt               lt id gt appengine-api-stubs lt  id gt               lt phase gt initialize lt  phase gt               lt goals gt                   lt goal gt install-file lt  goal gt               lt  goals gt               lt configuration gt                   lt groupId gt com local jar lt  groupId gt                   lt artifactId gt appengine-api-stubs lt  artifactId gt                   lt version gt 1 0 lt  version gt                   lt packaging gt jar lt  packaging gt                   lt file gt   local sdk  lib impl appengine-api-stubs jar lt  file gt               lt  configuration gt           lt  execution gt       lt  executions gt   lt  plugin gt    Finally  in dependencies  you can add the jars   lt dependency gt       lt groupId gt com local jar lt  groupId gt       lt artifactId gt appengine-api lt  artifactId gt       lt version gt 1 0 lt  version gt   lt  dependency gt    lt dependency gt       lt groupId gt com local jar lt  groupId gt       lt artifactId gt appengine-api-stubs lt  artifactId gt       lt version gt 1 0 lt  version gt       lt scope gt test lt  scope gt   lt  dependency gt    By Setting up your project like this  the project will continue to build even when you take it to another computer  given that it has all the jar files in the path specified by the property local sdk    For groupId use a unique name just to make sure that there are no conflicts   Now when you mvn install or mvn test local jars will be added automatically

User · Answer

Step 1  Configure the maven-install-plugin with the goal install-file in your pom xml   lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-install-plugin lt  artifactId gt       lt executions gt           lt execution gt               lt id gt install-external-non-maven-jar-MWS-Client-into-local-maven-repo lt  id gt               lt phase gt clean lt  phase gt               lt configuration gt                   lt repositoryLayout gt default lt  repositoryLayout gt                   lt groupId gt com amazonservices mws lt  groupId gt                   lt artifactId gt mws-client lt  artifactId gt                   lt version gt 1 0 lt  version gt                   lt file gt   project basedir  lib MWSClientJavaRuntime-1 0 jar lt  file gt                   lt packaging gt jar lt  packaging gt                   lt generatePom gt true lt  generatePom gt               lt  configuration gt               lt goals gt                   lt goal gt install-file lt  goal gt               lt  goals gt           lt  execution gt       lt  executions gt   lt  plugin gt    Make sure to edit the file path based on your actual file path  recommended is to place these external non-maven jars inside some folder  let s say lib  and place this lib folder inside your project so as to use project-specific relative path and avoid adding system specific absolute path   If you have multiple external jars  just repeat the  lt execution gt  for other jars within the same maven-install-plugin   Step 2  Once you have configured the maven-install-plugin as shown above in your pom xml file  you have to use these jars in your pom xml as usual        lt dependency gt           lt groupId gt com amazonservices mws lt  groupId gt           lt artifactId gt mws-client lt  artifactId gt           lt version gt 1 0 lt  version gt       lt  dependency gt    Note that the maven-install-plugin only copies your external jars to your local  m2 maven repository  That s it  It doesn t automatically include these jars as maven dependencies to your project   It s a minor point  but sometimes easy to miss

User · Answer

The preferred way would be to create your own remote repository   See here for details on how to do it  Have a look at the  Uploading to a Remote Repository  section

User · Answer

Another interesting case is when you want to have in your project private maven jars  You may want to keep the capabilities of Maven to resolve transitive dependencies  The solution is fairly easy    Create a folder libs in your project Add the following lines in your pom xml file   lt properties gt  lt local repository folder gt   pom basedir  libs  lt  local repository folder gt   lt  properties gt    lt repositories gt      lt repository gt           lt id gt local-maven-repository lt  id gt           lt url gt file     local repository folder  lt  url gt           lt releases gt               lt enabled gt true lt  enabled gt           lt  releases gt           lt snapshots gt               lt enabled gt true lt  enabled gt           lt  snapshots gt      lt  repository gt   lt  repositories gt   Open the  m2 repository folder and copy the directory structure of the project you want to import into the libs folder     E g  suppose you want to import the dependency   lt dependency gt       lt groupId gt com mycompany myproject lt  groupId gt       lt artifactId gt myproject lt  artifactId gt       lt version gt 1 2 3 lt  version gt   lt  dependency gt    Just go on  m2 repository and you will see the following folder  com mycompany myproject 1 2 3  Copy everything in your libs folder  again  including the folders under  m2 repository  and you are done

User · Answer

Add your own local JAR in POM file and use that in maven build   mvn install install-file -Dfile path-to-jar -DgroupId owngroupid -DartifactId ownartifactid -Dversion ownversion -Dpackaging jar   For example   mvn install install-file -Dfile path-to-jar -DgroupId com decompiler -DartifactId jd-core-java -Dversion 1 2 -Dpackaging jar   Then add it to the POM like this

User · Answer

You can add local dependencies directly  as mentioned in build maven project with propriatery libraries included  like this    lt dependency gt       lt groupId gt com sample lt  groupId gt       lt artifactId gt sample lt  artifactId gt       lt version gt 1 0 lt  version gt       lt scope gt system lt  scope gt       lt systemPath gt   project basedir  src main resources Name Your JAR jar lt  systemPath gt   lt  dependency gt    Update  In new releases this feature is marked as deprecated but still working and not removed yet   You just see warning in the log during maven start   An issue is raised at maven group about this https   issues apache org jira browse MNG-6523   You can participate and describe why this feature is helpful in some cases   I hope this feature remains there    If you are asking me  as long as the feature is not removed  I use this to make dependency to only one naughty jar file in my project which is not fit in repository  If this feature is removed  well  there are lots of good answers here which I can chose from later

User · Answer

I d like such solution - use maven-install-plugin in pom file    lt plugin gt       lt groupId gt org apache maven plugins lt  groupId gt       lt artifactId gt maven-install-plugin lt  artifactId gt       lt version gt 2 5 2 lt  version gt       lt executions gt           lt execution gt               lt phase gt initialize lt  phase gt               lt goals gt                   lt goal gt install-file lt  goal gt               lt  goals gt               lt configuration gt                   lt file gt lib yourJar jar lt  file gt                   lt groupId gt com somegroup id lt  groupId gt                   lt artifactId gt artefact-id lt  artifactId gt                   lt version gt x y z lt  version gt                   lt packaging gt jar lt  packaging gt               lt  configuration gt           lt  execution gt       lt  executions gt   lt  plugin gt    In this case you can perform mvn initialize and jar will be installed in local maven repo  Now this jar is available during any maven step on this machine  do not forget to include this dependency as any other maven dependency in pom with  lt dependency gt  lt  dependency gt  tag   It is also possible to bind jar install not to initialize step  but any other step you like

User · Answer

Important part in dependency is    pom basedir   instead of just   basedir     lt dependency gt       lt groupId gt org example lt  groupId gt       lt artifactId gt example lt  artifactId gt       lt version gt 1 0 lt  version gt       lt scope gt system lt  scope gt       lt systemPath gt   pom basedir  src lib example jar lt  systemPath gt   lt  dependency gt

User · Answer

My shaded jar file did not contain the third-party library using AlirezaFattahi s solution  however  I remeber that it was working once I had tried it for the same project last time  So  I tried my own solution   mkdir the project s path under  m2 repositories directory  similar to other maven dependencies directory at that directory  put the third-party jar file in it  add the dependency as like as the libraries on a maven repository   Finally  It worked for me

User · Answer

For some reason  in the web application I m giving maintenance to  neither Alireza Fattahi s solution nor JJ Roman s solution worked correctly  In both cases  the compilation goes okay  it sees the jar   but the packaging fails to include the jar inside the war   The only way I managed to make it work was by putting the jar on  src main webapp WEB-INF lib  and then combining it with either Fattahis s or Roman s solution

User · Answer

Create a new folder  let s say local-maven-repo at the root of your Maven project   Just add a local repo inside your  lt project gt  of your pom xml    lt repositories gt       lt repository gt           lt id gt local-maven-repo lt  id gt           lt url gt file      project basedir  local-maven-repo lt  url gt       lt  repository gt   lt  repositories gt    Then for each external jar you want to install  go at the root of your project and execute   mvn deploy deploy-file -DgroupId  GROUP  -DartifactId  ARTIFACT  -Dversion  VERS  -Durl file   local-maven-repo  -DrepositoryId local-maven-repo -DupdateReleaseInfo true -Dfile  FILE PATH

User · Answer

To install third party jar  Please call the command like below  mvn install install-file -DgroupId  -DartifactId  -Dversion  -Dpackaging jar -Dfile path

User · Answer

Add local jar libraries  their sources and javadoc to a Maven project If you have pre-compiled jar files with libraries  their sources and javadoc  then you can install them to your local Maven repository like this   mvn install install-file     -Dfile awesomeapp-1 0 1 jar       -DpomFile awesomeapp-1 0 1 pom       -Dsources awesomeapp-1 0 1-sources jar       -Djavadoc awesomeapp-1 0 1-javadoc jar       -DgroupId com example       -DartifactId awesomeapp       -Dversion 1 0 1       -Dpackaging jar  Then in your project you can use this libraries   lt  -- com example -- gt   lt dependency gt       lt groupId gt com example lt  groupId gt       lt artifactId gt awesomeapp lt  artifactId gt       lt version gt 1 0 1 lt  version gt   lt  dependency gt   See  maven-install-plugin usage   Or you can build these libraries yourself with their sources and javadoc using maven-source-plugin and maven-javadoc-plugin  and then install them  Example project  library  lt  xml version  quot 1 0 quot  encoding  quot UTF-8 quot   gt   lt project xmlns  quot http   maven apache org POM 4 0 0 quot           xmlns xsi  quot http   www w3 org 2001 XMLSchema-instance quot           xsi schemaLocation  quot http   maven apache org POM 4 0 0          http   maven apache org xsd maven-4 0 0 xsd quot  gt       lt modelVersion gt 4 0 0 lt  modelVersion gt        lt url gt https   example com awesomeapp lt  url gt        lt groupId gt com example lt  groupId gt       lt artifactId gt awesomeapp lt  artifactId gt       lt name gt awesomeapp lt  name gt       lt version gt 1 0 1 lt  version gt       lt packaging gt jar lt  packaging gt        lt properties gt           lt java version gt 12 lt  java version gt       lt  properties gt        lt build gt           lt finalName gt awesomeapp lt  finalName gt           lt defaultGoal gt install lt  defaultGoal gt            lt plugins gt               lt plugin gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-compiler-plugin lt  artifactId gt                   lt version gt 3 8 1 lt  version gt                   lt configuration gt                       lt source gt   java version  lt  source gt                       lt target gt   java version  lt  target gt                       lt encoding gt UTF-8 lt  encoding gt                   lt  configuration gt               lt  plugin gt               lt plugin gt                   lt inherited gt true lt  inherited gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-source-plugin lt  artifactId gt                   lt version gt 3 2 1 lt  version gt                   lt executions gt                       lt execution gt                           lt id gt attach-sources lt  id gt                           lt goals gt  lt goal gt jar lt  goal gt  lt  goals gt                       lt  execution gt                   lt  executions gt               lt  plugin gt               lt plugin gt                   lt inherited gt true lt  inherited gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-javadoc-plugin lt  artifactId gt                   lt version gt 3 2 0 lt  version gt                   lt executions gt                       lt execution gt                           lt id gt attach-javadocs lt  id gt                           lt goals gt  lt goal gt jar lt  goal gt  lt  goals gt                       lt  execution gt                   lt  executions gt               lt  plugin gt           lt  plugins gt       lt  build gt   lt  project gt   Execute maven install goal  mvn install  Check your local Maven repository     m2 repository com example awesomeapp 1 0 1    -  remote repositories   - awesomeapp-1 0 1 jar   - awesomeapp-1 0 1 pom   - awesomeapp-1 0 1-javadoc jar   - awesomeapp-1 0 1-sources jar  Then you can use this library   lt  -- com example -- gt   lt dependency gt       lt groupId gt com example lt  groupId gt       lt artifactId gt awesomeapp lt  artifactId gt       lt version gt 1 0 1 lt  version gt   lt  dependency gt

User · Answer

This is a short syntax for newer versions   mvn install install-file -Dfile  lt path-to-file gt    It works when the JAR was built by Apache Maven - the most common case  Then it ll contain a pom xml in a subfolder of the META-INF directory  which will be read by default   Source  http   maven apache org guides mini guide-3rd-party-jars-local html

User · Answer

command line    mvn install install-file -Dfile c  kaptcha- version  jar -DgroupId com google code -DartifactId kaptcha -Dversion  version  -Dpackaging jar

User · Answer

Also take a look at      lt scope gt compile lt  scope gt    Maven Dependencies   This is the default but I ve found in some cases explicitly setting that scope also Maven to find local libraries in the local repository

User · Answer

I want to share a code where you can upload a folder full of jars  It s useful when a provider doesn t have a public repository and you need to add lots of libraries  manually  I ve decided to build a  bat instead of call directly to maven because It could be Out of Memory errors  It was prepared for a windows environment but is easy to adapt it to linux OS   import java io File  import java io IOException  import java io PrintWriter  import java util Date  import java util jar Attributes  import java util jar JarFile  import java util jar Manifest   public class CreateMavenRepoApp        private static final String OCB PLUGIN FOLDER    C   your folder with jars        public static void main String   args  throws IOException        File directory   new File          get all the files from a directory     PrintWriter writer   new PrintWriter  update repo maven bat    UTF-8        writer println  rem    new Date           File   fList   directory listFiles        for  File file   fList           if  file isFile                            String absolutePath   file getAbsolutePath             Manifest  m   new JarFile absolutePath  getManifest            Attributes attributes   m getMainAttributes            String symbolicName   attributes getValue  Bundle-SymbolicName             if symbolicName  null  amp  amp symbolicName contains  com yourCompany yourProject                  String   parts  symbolicName split                     String artifactId   parts parts length-1               String groupId   symbolicName substring 0 symbolicName length  -artifactId length  -1               String version   attributes getValue  Bundle-Version                String mavenLine   call mvn org apache maven plugins maven-install-plugin 2 5 1 install-file -Dfile    absolutePath   -DgroupId    groupId   -DartifactId    artifactId   -Dversion    version   -Dpackaging jar                writer println mavenLine                                            writer close               After run this main from any IDE  run the update repo maven bat

User · Answer

The really quick and dirty way is to point to a local file    lt dependency gt         lt groupId gt sample lt  groupId gt            lt artifactId gt com sample lt  artifactId gt            lt version gt 1 0 lt  version gt          lt scope gt system lt  scope gt         lt systemPath gt C  DEV myfunnylib yourJar jar lt  systemPath gt   lt  dependency gt    However this will only live on your machine  obviously   for sharing it usually makes sense to use a proper m2 archive  nexus artifactory  or if you do not have any of these or don t want to set one up a local maven structured archive and configure a  repository  in your pom  local    lt repositories gt       lt repository gt           lt id gt my-local-repo lt  id gt           lt url gt file   C  DEV  mymvnrepo lt  url gt       lt  repository gt   lt  repositories gt    remote    lt repositories gt       lt repository gt           lt id gt my-remote-repo lt  id gt           lt url gt http   192 168 0 1 whatever mavenserver youwant repo lt  url gt       lt  repository gt   lt  repositories gt    for this a relative path is also possible using the basedir variable    lt url gt file   basedir  lt  url gt

User · Answer

Perhaps someone will be interested in  https   github com Limraj maven-artifact-generator Console program to generate maven artifacts in the local repository  and configure dependencies for pom xml  based on the path to the jars  You can do this for one file  but it s most useful if you have multiple jar files  path jars  java -jar maven-artifact-generator-X X X jar -p path to jars -g com test -V 1 2 3 -P jar jar  java -jar maven-artifact-generator-X X X jar -f file jar -g com test -V 1 2 3 -P jar This will generate an artifact in the local maven repository  and generate dependecies for pom xml in gen log  ArtifactId is the name of the jar file  Requires an installed maven  Testing on widnows 7 and macOS X  unix linux

User · Answer

Install the JAR into your local Maven repository as follows   mvn install install-file      -Dfile  lt path-to-file gt       -DgroupId  lt group-id gt       -DartifactId  lt artifact-id gt       -Dversion  lt version gt       -Dpackaging  lt packaging gt       -DgeneratePom true   Where each refers to     lt path-to-file gt   the path to the file to load e g   c  kaptcha-2 3 jar   lt group-id gt   the group that the file should be registered under e g   com google code   lt artifact-id gt   the artifact name for the file e g   kaptcha   lt version gt   the version of the file e g   2 3   lt packaging gt   the packaging of the file e g    jar  Reference   Maven FAQ  I have a jar that I want to put into my local repository  How can I copy it in  Maven Install Plugin Usage  The install install-file goal

User · Answer

Firstly  I would like to give credit for this answer to an anonymous Stack Overflow user - I am pretty sure I ve seen a similar answer here before - but now I cannot find it    The best option for having local JAR files as a dependency is to create a local Maven repository  Such a repository is nothing more than a proper directory structure with pom files in it    For my example  I have my master project on   master project  location and subproject1 is on   master project    subproject1    Then I create a Maven repository in    master project  local-maven-repo   In the pom file in subproject1 located at   master project    subproject1  pom xml  the repository needs to be specified which would take file path as a URL parameter    lt repositories gt       lt repository gt           lt id gt local-maven-repo lt  id gt           lt url gt file      project parent basedir  local-maven-repo lt  url gt       lt  repository gt   lt  repositories gt    The dependency can be specified as for any other repository  This makes your pom repository independent  For instance  once the desired JAR is available in Maven central  you just need to delete it from your local repo and it will be pulled from the default repo         lt dependency gt           lt groupId gt org apache felix lt  groupId gt           lt artifactId gt org apache felix servicebinder lt  artifactId gt           lt version gt 0 9 0-SNAPSHOT lt  version gt       lt  dependency gt    The last but not least thing to do is to add the JAR file to local repository using -DlocalRepositoryPath switch like so   mvn org apache maven plugins maven-install-plugin 2 5 2 install-file        -Dfile  some path on my local filesystem felix servicebinder target org apache felix servicebinder-0 9 0-SNAPSHOT jar       -DgroupId org apache felix -DartifactId org apache felix servicebinder       -Dversion 0 9 0-SNAPSHOT -Dpackaging jar       -DlocalRepositoryPath   master project  local-maven-repo   Once the JAR file is installed  your Maven repo can be committed to a code repository  and the whole set-up is system independent   Working example in GitHub    I agree that having JARs committed to source code repo is not a good practice  but in real life  quick and dirty solutions are sometimes better than a full blown Nexus repo to host one JAR that you cannot publish

User · Answer

Not an answer to the original question  however it might be useful for someone There is no proper way to add multiple jar libraries from the folder using Maven  If there are only few dependencies  it is probably easier to configure maven-install-plugin as mentioned in the answers above  However for my particular case  I had a lib folder with more than 100 proprietary jar files which I had to add somehow  And for me it was much easier for me to convert my Maven project to Gradle  plugins       id  org springframework boot  version  2 2 2 RELEASE      id  io spring dependency-management  version  1 0 8 RELEASE      id  java     group    com example  version    0 0 1-SNAPSHOT  sourceCompatibility    1 8   repositories       mavenCentral       flatDir          dirs  libs     local libs folder         dependencies       implementation  org springframework boot spring-boot-starter-web      testImplementation  org springframework boot spring-boot-starter-test             exclude group   org junit vintage   module   junit-vintage-engine                 implementation  io grpc grpc-netty-shaded 1 29 0      implementation  io grpc grpc-protobuf 1 29 0      implementation  io grpc grpc-stub 1 29 0     dependecies from maven central      implementation name   akka-actor 2 12-2 6 1     dependecies from lib folder     implementation name   akka-protobuf-v3 2 12-2 6 1      implementation name   akka-stream 2 12-2 6 1

User · Answer

Yes   you can have but its not good idea   Instead install all these jars to maven repos  Also See   How to build maven project with propriatery libraries included

User · Answer

In Apache Maven 3 5 4  I had to add double quotation  Without double quotation it wasn t worked for me   example      mvn install install-file  -Dfile location to the jar file   -DgroupId group id   -DartifactId artifact id   -Dversion version   -Dpackaging package type

User · Answer

One way is to upload it to your own Maven repository manager  such as Nexus   It s good practice to have an own repository manager anyway   Another nice way I ve recently seen is to include the Maven Install Plugin in your build lifecycle  You declare in the POM to install the files to the local repository  It s a little but small overhead and no manual step involved   http   maven apache org plugins maven-install-plugin install-file-mojo html

User · Answer

Of course you can add jars to that folder  But maybe it does not what you want to achieve     If you need these jars for compilation  check this related question  Can I add jars to maven 2 build classpath without installing them   Also  before anyone suggests it  do NOT use the system scope

User · Answer

I had the same error for a set of dependencies in my pom xml turns out the versions of the dependencies was not specified in the pom xml and was mentioned in the parent repository  For some reason the version details was not syncing with this repo  Hence i manually entered the versions using the  tag and it worked like a charm  Little bit of time needed to look up the versions in the parent and specify here  But this can be done just for the jars that are showing the artifactid error and it works  Hope this helps someone

User · Answer

Note that it is NOT necessarily a good idea to use a local repo  If this project is shared with others then everyone else will have problems and questions when it doesn t work  and the jar won t be available even in your source control system   Although the shared repo is the best answer  if you cannot do this for some reason then embedding the jar is better than a local repo  Local-only repo contents can cause lots of problems  especially over time

[java] How to add local jar files to a Maven project?

Examples related to java

Examples related to maven

Examples related to dependencies

Examples related to libraries

Examples related to mvn-repo