Bug 808704

Summary: beust-jcommander-1.30 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: beust-jcommanderAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: java-sig-commits, jcapik
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 1.30-1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 09:59:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 888233    

Description Upstream Release Monitoring 2012-03-31 10:04:10 UTC
Latest upstream release: 1.23
Current version in Fedora Rawhide: 1.17
URL: https://github.com/cbeust/jcommander/tags

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Upstream Release Monitoring 2012-04-29 10:05:49 UTC
Latest upstream release: 1.25
Current version in Fedora Rawhide: 1.17
URL: https://github.com/cbeust/jcommander/tags

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 2 Upstream Release Monitoring 2012-06-03 21:44:16 UTC
Latest upstream release: 1.26
Current version in Fedora Rawhide: 1.17
URL: https://github.com/cbeust/jcommander/tags

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 3 Upstream Release Monitoring 2012-07-06 06:53:49 UTC
Latest upstream release: 1.27
Current version in Fedora Rawhide: 1.17
URL: https://github.com/cbeust/jcommander/tags

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 4 Upstream Release Monitoring 2012-07-29 09:30:10 UTC
Latest upstream release: 1.29
Current version in Fedora Rawhide: 1.17
URL: https://github.com/cbeust/jcommander/tags

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 5 Upstream Release Monitoring 2012-10-27 19:04:49 UTC
Latest upstream release: 1.30
Current version in Fedora Rawhide: 1.17
URL: https://github.com/cbeust/jcommander/tags

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 6 Mikolaj Izdebski 2013-01-10 09:59:22 UTC
I believe that this bug is fixed in beust-jcommander-1.30-1,
which is available in Fedora Rawhide.  I am closing the bug now,
thank you for reporting it.  A summary of changes is included below.

* Thu Jan 10 2013 Mikolaj Izdebski <mizdebsk> - 1.30-1
- Update to upstream version 1.30
- Build with xmvn