Maven and adding JARs to system scope

Question

I have a JAR in my Android project and I want it to be added to final APK  Okay  here I go        lt dependency gt           lt groupId gt com loopj android http lt  groupId gt           lt artifactId gt android-async-http lt  artifactId gt           lt version gt 1 3 2 lt  version gt           lt type gt jar lt  type gt           lt scope gt system lt  scope gt           lt systemPath gt   project basedir  libs android-async-http-1 3 2 jar lt  systemPath gt       lt  dependency gt    But when I am running mvn package I am getting a warning    WARNING  Some problems were encountered while building the effective model for   apk 1 0  WARNING   dependencies dependency systemPath  for com loopj android http android-async-http jar should not point at files within the project directory    project basedir  libs android-async-http-1 3 2 jar will be unresolvable by dependent projects   line 36  column 25   And in the final APK there are no JARs   How do I fix that

User · Accepted Answer

You will need to add the jar to your local maven repository. Alternatively (better option) specify the proper repository (if one exists) so it can be automatically downloaded by maven

In either case, remove the <systemPath> tag from the dependency

User · Answer

System scope was only designed to deal with  system  files  files sitting in some fixed location  Files in  usr lib  or   java home   e g  tools jar   It wasn t designed to support miscellaneous  jar files in your project   The authors intentionally refused to make the pathname expansions work right for that to discourage you  As a result  in the short term you can use install install-file to install into the local repo  and then some day use a repo manager to share

User · Answer

Try this configuration  It worked for me     lt plugin gt       lt artifactId gt maven-war-plugin lt  artifactId gt       lt version gt 2 4 lt  version gt       lt configuration gt           lt warSourceDirectory gt mywebRoot lt  warSourceDirectory gt           lt warSourceExcludes gt source    build    dist    WEB-INF lib                WEB-INF classes    build            lt  warSourceExcludes gt           lt webXml gt myproject source deploiement web xml lt  webXml gt           lt webResources gt               lt resource gt                   lt directory gt mywebRoot WEB-INF lib lt  directory gt                   lt targetPath gt WEB-INF lib lt  targetPath gt                   lt includes gt                           lt include gt mySystemJar1 jar jar lt  include gt                            lt include gt mySystemJar2 jar lt  include gt                      lt  includes gt               lt  resource gt           lt  webResources gt       lt  configuration gt   lt  plugin gt

User · Answer

mvn install install-file -DgroupId com paic maven -DartifactId tplconfig-maven-plugin -Dversion 1 0 -Dpackaging jar -Dfile tplconfig-maven-plugin-1 0 jar -DgeneratePom true  Install the jar to local repository

User · Answer

lt plugin gt       lt groupId gt org springframework boot lt  groupId gt       lt artifactId gt spring-boot-maven-plugin lt  artifactId gt       lt configuration gt           lt includeSystemScope gt true lt  includeSystemScope gt       lt  configuration gt   lt  plugin gt    Try this

User · Answer

I don t know the real reason but Maven pushes developers to install all libraries  custom too  into some maven repositories  so scope system is not well liked  A simple workaround is to use maven-install-plugin  follow the usage   write your dependency in this way   lt dependency gt       lt groupId gt com mylib lt  groupId gt       lt artifactId gt mylib-core lt  artifactId gt       lt version gt 0 0 1 lt  version gt   lt  dependency gt    then  add maven-install-plugin   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 install-external lt  id gt               lt phase gt clean lt  phase gt               lt configuration gt                   lt file gt   basedir  lib mylib-core-0 0 1 jar lt  file gt                   lt repositoryLayout gt default lt  repositoryLayout gt                   lt groupId gt com mylib lt  groupId gt                   lt artifactId gt mylib-core lt  artifactId gt                   lt version gt 0 0 1 lt  version 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    pay attention to phase clean  to install your custom library into your repository  you have to run mvn clean and then mvn install

User · Answer

Thanks to Ging3r i got solution   follow these steps    don t use  in dependency tag  Use following in dependencies tag in pom xml file     lt dependency gt   lt groupId gt com netsuite suitetalk proxy v2019 1 lt  groupId gt   lt artifactId gt suitetalk-axis-proxy-v2019 1 lt  artifactId gt   lt version gt 1 0 0 lt  version gt   lt  dependency gt   lt dependency gt       lt groupId gt com netsuite suitetalk client v2019 1 lt  groupId gt       lt artifactId gt suitetalk-client-v2019 1 lt  artifactId gt       lt version gt 2 0 0 lt  version gt   lt  dependency gt   lt dependency gt       lt groupId gt com netsuite suitetalk client common lt  groupId gt       lt artifactId gt suitetalk-client-common lt  artifactId gt       lt version gt 1 0 0 lt  version gt   lt  dependency gt   use following code in plugins tag in pom xml 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 id gt suitetalk-proxy lt  id gt                   lt phase gt clean lt  phase gt                   lt configuration gt                       lt file gt   basedir  lib suitetalk-axis-proxy-v2019 1-1 0 0 jar lt  file gt                       lt repositoryLayout gt default lt  repositoryLayout gt                       lt groupId gt com netsuite suitetalk proxy v2019 1 lt  groupId gt                       lt artifactId gt suitetalk-axis-proxy-v2019 1 lt  artifactId gt                       lt version gt 1 0 0 lt  version 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 execution gt                   lt id gt suitetalk-client lt  id gt                   lt phase gt clean lt  phase gt                   lt configuration gt                       lt file gt   basedir  lib suitetalk-client-v2019 1-2 0 0 jar lt  file gt                       lt repositoryLayout gt default lt  repositoryLayout gt                       lt groupId gt com netsuite suitetalk client v2019 1 lt  groupId gt                       lt artifactId gt suitetalk-client-v2019 1 lt  artifactId gt                       lt version gt 2 0 0 lt  version 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 execution gt                   lt id gt suitetalk-client-common lt  id gt                   lt phase gt clean lt  phase gt                   lt configuration gt                       lt file gt   basedir  lib suitetalk-client-common-1 0 0 jar lt  file gt                       lt repositoryLayout gt default lt  repositoryLayout gt                       lt groupId gt com netsuite suitetalk client common lt  groupId gt                       lt artifactId gt suitetalk-client-common lt  artifactId gt                       lt version gt 1 0 0 lt  version 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     I am including 3 jars from lib folder     Finally  use mvn clean and then mvn install or  mvn clean install  and just run jar file from target folder or the path where install see mvn install log    java -jar abc jar  note  Remember one thing if you are working at jenkins then first use mvn clean and then mvn clean install command work for you because with previous code mvn clean install command store cache for dependency

User · Answer

Use a repository manager and install this kind of jars into it  That solves your problems at all and for all computers in your network

[maven] Maven and adding JARs to system scope

Examples related to maven