i

impex-legacy-bundle

This project creates a bundle of the Impex legacy tool that is decoupled from Subversion. It creates a jar file that has the exact same binaries, source, directory structure, and layout as the Impex contained inside Subversion. Since it is published as a versioned jar file, it can be referenced in other processes (like the Rice binary release process) without those processes needing the ability to connect back to Subversion to check out the tool. Processes that need access to the legacy Impex tool can thus express a normal maven dependency in order to obtain it.
need binary maven other connect tool normal contained since creates from express same needing dependency order subversion file exact layout bundle impex published ability processes structure those rice check binaries thus back decoupled like access versioned referenced without process project that obtain source directory inside this release legacy
Files download
File Operation
impex-legacy-bundle-1.0.0.jar download
impex-legacy-bundle-1.0.0.pom download
impex-legacy-bundle-1.0.0-sources.jar download
Apache Maven 
<dependency>
  <groupId>org.kuali.db.impex</groupId>
  <artifactId>impex-legacy-bundle</artifactId>
  <version>1.0.0</version>
</dependency>
Gradle Groovy 
implementation 'org.kuali.db.impex:impex-legacy-bundle:1.0.0'
Gradle Kotlin 
implementation("org.kuali.db.impex:impex-legacy-bundle:1.0.0")
Scala SBT 
libraryDependencies += "org.kuali.db.impex" % "impex-legacy-bundle" % "1.0.0"
Groovy Grape 
@Grapes(
  @Grab(group='org.kuali.db.impex', module='impex-legacy-bundle', version='1.0.0')
)
Apache Ivy 
<dependency org="org.kuali.db.impex" name="impex-legacy-bundle" rev="1.0.0" />
Leiningen 
[org.kuali.db.impex/impex-legacy-bundle "1.0.0"]
Apache Buildr 
'org.kuali.db.impex:impex-legacy-bundle:jar:1.0.0'
Dependencies 
<parent>
  <groupId>org.kuali</groupId>
  <artifactId>kuali-common</artifactId>
  <version>22</version>
</parent>
The project has no third-party dependencies