Home > Back-end >  Java maven part with only rely on packaging?
Java maven part with only rely on packaging?

Time:09-22

Such as my pom is



Org. Hbase
Asynchbase
1.7.1 & lt;/version>




Org. Apache. Thrift
Libthrift
& lt; Version> 0.8.0 & lt;/version>



Rely on hbase and thrift

MVN package and thrift dependent jar don't need to hbase should rely on pom in how to write

CodePudding user response:

Don't rely on add
Test

CodePudding user response:

Upstairs positive solution and add the & lt; Scope> The value of the meaning of:

Compile, default values, applicable to all phases, will be released as the project together,
Provided, similar to the compile, expect the JDK, container or the user will provide the dependencies, such as servlets. Jar,
Runtime, only used at run time, such as the JDBC driver, apply to run and test phase,
test, only used in test, used to compile and run the test code, not project, along with the
System, similar to provided, it is necessary to explicitly provide contain dependent jar, Maven will not find it in the Repository,

http://peak.iteye.com/blog/299225

CodePudding user response:

CodePudding user response:


Org. Hbase
Asynchbase
1.7.1 & lt;/version>
Provided




Org. Apache. Thrift
Libthrift
0.8.0 & lt;/version>


As above, in hbase rely on add & lt; Scope> Provided Ok, you can search for specific usage Maven Dependency Scope usage,
  • Related