Bug 696568

Summary: jline-1.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: jlineAssignee: Mat Booth <mat.booth>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: akurtako, mat.booth, ville.skytta
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-01 21:04:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Upstream Release Monitoring 2011-04-14 10:30:36 UTC
Latest upstream release: 1.0
Current version in Fedora Rawhide: 0.9.94
URL: http://sourceforge.net/projects/jline/files/

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 Ville Skyttä 2011-07-10 14:45:24 UTC
I updated to 1.0 locally, and found that it works significantly worse than 0.9.94 for me with bsh and gnome-terminal; it seems that it doesn't recognize the bsh prompt at all - for example Ctrl-A really goes to the beginning of the line instead of stopping where the prompt ends, and other actions behave similarly as if the prompt didn't exist.  I didn't find an obvious cause in a 1 minute skim through the diffs, so maybe it's better to stick with 0.9.94 for now.

Comment 2 Alexander Kurtakov 2012-02-01 21:04:28 UTC
I have pushed to 1.0 before seeing this bug. The reason for doing this was because jruby builds against 1.0 and I wanted to minimize build differencies.

Comment 3 Ville Skyttä 2012-02-05 10:10:12 UTC
(In reply to comment #2)
> I have pushed to 1.0 before seeing this bug. The reason for doing this was
> because jruby builds against 1.0 and I wanted to minimize build differencies.

Hopefully there's someone to fix the issues jline 1.0 has with bsh then; in my earlier tests the update made things essentially useless with bsh whereas with 0.9.94 they worked just fine.  If there's nobody around to do that and the jline update was made essentially just for cosmetic reasons, I suggest reverting the update and pushing 0.9.94 back with an epoch bump.