x

xapi-jre

This module exists solely to package all other jre modules into a single uber jar. This makes deploying to non-mavenized targets much easier. Of course, you would be wise to inherit your dependencies individually; the uber jar is intended for projects like collide, which have complex configuration, and adding many jars would be a pain. It also allows dependent modules to discover new features, as modules graduate from labs to final, they will be added here. As you type X_, autocomplete will expose newly added services.
WeTheInter.net
they newly single wise package type deploying course would expose solely features collide final services easier discover here inherit like intended much many projects labs individually mavenized will this complex other have dependent pain uber from dependencies allows graduate targets jars module added makes your into autocomplete which exists configuration modules also adding
文件下载
文件名 操作
xapi-jre-0.5.jar 下载
xapi-jre-0.5.pom 下载
xapi-jre-0.5-sources.jar 下载
Apache Maven 
<dependency>
  <groupId>net.wetheinter</groupId>
  <artifactId>xapi-jre</artifactId>
  <version>0.5</version>
</dependency>
Gradle Groovy 
implementation 'net.wetheinter:xapi-jre:0.5'
Gradle Kotlin 
implementation("net.wetheinter:xapi-jre:0.5")
Scala SBT 
libraryDependencies += "net.wetheinter" % "xapi-jre" % "0.5"
Groovy Grape 
@Grapes(
  @Grab(group='net.wetheinter', module='xapi-jre', version='0.5')
)
Apache Ivy 
<dependency org="net.wetheinter" name="xapi-jre" rev="0.5" />
Leiningen 
[net.wetheinter/xapi-jre "0.5"]
Apache Buildr 
'net.wetheinter:xapi-jre:jar:0.5'
本项目依赖 
<parent>
  <groupId>net.wetheinter</groupId>
  <artifactId>xapi-jre-parent</artifactId>
  <version>0.5</version>
</parent>

test

|-- net.wetheinter:xapi-core-test:0.5