MavenToPKGBUILD

Create packages for Arch linux (AUR) for Maven dependencies.

The packages are installed in /usr/share/java, as it is recommended in the PKGBUILD for java guide. For now and in the future I try to stick to the official guidelines.

This is a first implementation to manage dependencies for java programs that share jar files. The goal is to distribute java programs and its dependencies separated in a clean way. However the current risk is that we have to create dozens or hundreds of packages for large projects.

Please do not submit the generated PKGBUILDs to the ArchLinux repository without filling out all the required informations.

How to use

1. Build a specific project:

pkg-maven DATABASE.yaml PROJECT

You can try it:

pkg-maven package.yaml jedis

2. Build all the projects:

Create a package for each dependency in the database. It is quite simple for now and does not handle double entry or version conflicts.

pkg-maven DATABASE.yaml all

You can try it:

pkg-maven package.yaml all

3. Build a package by its name.

You can also try it:

pkg-maven jedis redis.clients 2.9.0

This will create a package for one jar only. You can get get its dependencies by going in the folder and running the pkg-maven-list-deps script. 

cd jedis
pkg-maven-list-deps jedis.yaml   ## here jedis.yaml is the output file name, the default is deps.yaml

You can then use the jedis.yaml to create more packages !

If the generated name does not seem correct, you can add a name field: 

jedis:
  groupid: redis.clients
  artifactid: jedis
  version: 2.9.0
  name: redis

With this modification, the package name will be: java-redis.

Options

There are three ways to build a package. Either you want to package a specific jar, a jar with packages for each dependency, or a jar with its dependency included in one big jar.

Installing a package

After the package(s) are built, you can install it with pacman.

Here is an example:

sudo pacman -U pkgs/java-jedis-2.9.0-1-any.pkg.tar.xz

Running an application

The program pkg-maven-list-deps creates a classpath.txt that contains all the dependencies. You can use this way: 

CP=$(<classpath.txt)
java -cp $CP:target/* tech.lity.rea.nectar.camera.Test

TODO:

  • Gemify this.
  • Better parsing.
  • Large scale tests.