Summary: | dev-java/jcommander - Command line parsing framework for Java | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | java, the.dmol |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/cbeust/jcommander | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 146226 | ||
Bug Blocks: | |||
Attachments: | jcommander-1.29_1.13.ebuild.diff |
Description
Diego Elio Pettenò (RETIRED)
2012-08-09 22:38:45 UTC
Created attachment 322446 [details, diff]
jcommander-1.29_1.13.ebuild.diff
Here is the ebuild diff for jcommander 1.13 which is required for testng-6.7
Seems this is already in the Portage tree, what will we do with this bug? Seems the testng bug is not resolved yet; though, it's kind of odd, since it depends on jcommander which causes a recursive dependency (or a dependency on an older version of itself). In other words, bootstrapping is needed in order to test; how are cases like this handled? Is this bug still open because of the missing testng dependency? commit 029aa0b (HEAD, master) Author: Patrice Clement <monsieurp@gentoo.org> Date: Sun Oct 25 14:31:19 2015 +0000 dev-java/jcommander: Version bump. Fixes bug 430688. Package-Manager: portage-2.2.20.1 Signed-off-by: Patrice Clement <monsieurp@gentoo.org> create mode 100644 dev-java/jcommander/files/jcommander-1.48-build.xml create mode 100644 dev-java/jcommander/jcommander-1.48.ebuild |