Package Details: picard-tools 2.24.1-1

Git Clone URL: (read-only, click to copy)
Package Base: picard-tools
Description: set of tools for working with next generation sequencing data in the BAM format
Upstream URL:
Licenses: MIT
Submitter: mschu
Maintainer: greyltc
Last Packager: greyltc
Votes: 8
Popularity: 0.65
First Submitted: 2013-11-25 11:23
Last Updated: 2021-01-22 16:47

Latest Comments

1 2 Next › Last »

luscinius commented on 2021-06-11 19:33

Fails to build in a chroot using aurutils, gradle complains about the maven plugin:

FAILURE: Build failed with an exception.

  • Where: Build file '/build/picard-tools/src/picard-2.24.1/build.gradle' line: 13

  • What went wrong: Plugin [id: 'maven'] was not found in any of the following sources:

  • Gradle Core Plugins (not a core plugin, please see for available core plugins)

  • Plugin Repositories (plugin dependency must include a version number for this source)

  • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at

wookietreiber commented on 2016-07-04 11:23

Done, thanks for letting me know, @greyltc.

greyltc commented on 2016-07-02 11:06

From the github repo's
As of version 2.0.1 (Nov. 2015) Picard requires Java 1.8 (jdk8u66). The last version to support Java 1.7 was release 1.141.

@wookietreiber, I think you need to update the dependencies here.

greyltc commented on 2016-07-02 10:56

I'm getting an "Unsupported major.minor version 52.0" error:

Exception in thread "main" java.lang.UnsupportedClassVersionError: picard/cmdline/PicardCommandLine : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(
at Method)
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
at sun.launcher.LauncherHelper.checkAndLoadMain(

wookietreiber commented on 2016-01-19 10:09

updated to 2.0.1

greyltc commented on 2015-03-18 14:33

Thanks for adding it.

I'm not sure how this issue could be addressed by upstream (outside of a line in the readme that says "For portability, packagers should export the PICARDROOT variable which points to the picard.jar install directory"), since the .jar install location on any given distro is up to the package maintainer.

wookietreiber commented on 2015-03-18 14:12

There is no harm in it. There is, however, harm in not involving the larger community.

greyltc commented on 2015-03-18 13:47

Oh come on. This should clearly be addressed by the packaging. What's the harm in adding the environment variable anyway?

wookietreiber commented on 2015-03-18 13:41

Then, for now, you should either do this in your bashrc / bash_profile only (or inside your build environment, however you are setting it up).

Considering the code you are writing: if you really want this to be portable, ask the picard-tools upstream devs to include such an environment variable for all to use in their project. Maybe they already have a solution for this issue.

greyltc commented on 2015-03-18 03:29

No, this variable is not required by any software that I'm aware of. It's a nice to have as a pointer to where the .jar files end up.

The script that this package includes is a nice way to call the tool in Arch, but I'm trying to write code that is portable to non-Arch environments where is not available. Having an environment variable created by the installer which tells the user where the tool was installed is a simple and elegant way to enable the user to write portable code.