Bug 1023736

Summary: JAR file should put into /usr/share/java/jline2/jline2.jar
Product: [Fedora] Fedora Reporter: Jochen Schmitt <jochen>
Component: jline2Assignee: Marek Goldmann <mgoldman>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jerboaa, mgoldman, mizdebsk, sgehwolf, sochotni
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-28 08:51:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Suggestion patch to solve the reported issue none

Description Jochen Schmitt 2013-10-27 14:12:35 UTC
Created attachment 816519 [details]
Suggestion patch to solve the reported issue

ON Rawhide the JAR file should be in

/usr/share/java/line2/jline2.ar

regrarding to the current Java packaging guidelines.

This is important, because the scala package create a symbolic link
to this JAR file.

Because there is a non-responsive package maintainer process agains the primary maintainer of this package, I plan to apply the suggestion patch as a provenpackager and start an addtional non-responsive maintainer process for this package too.

Comment 1 Jochen Schmitt 2013-10-27 14:15:43 UTC
Please forgett the last sentence about the non-responsive maintainership because I was accitendly in mind that jline2 has the same maintainer as the scala package.

Comment 2 Marek Goldmann 2013-10-28 08:51:28 UTC
Hi Jochen,

Currently we're in the process of renaming the jline* packages. jline will be renamed to jline1 and jline2 will be renamed to jline. Please see bug 1022897 for more info. After this the resulting package path will be following:

/usr/share/java/line/jline.jar

Having this in mind, I'm rejecting this bug report.

P.S. You shouldn't use manual symlinking *ever* in a spec file. There are tools for it like %mvn_install, %mvn_build, and %mvn_package macros, so I would reject your patch too.

Comment 3 Severin Gehwolf 2013-10-29 16:20:32 UTC
(In reply to Marek Goldmann from comment #2)
> Hi Jochen,
> 
> Currently we're in the process of renaming the jline* packages. jline will
> be renamed to jline1 and jline2 will be renamed to jline. Please see bug
> 1022897 for more info. After this the resulting package path will be
> following:
> 
> /usr/share/java/line/jline.jar

Small correction. It will be:
/usr/share/java/jline/jline.jar

However, I suggest to specify dependency on jline 2.x as follows (no need to know the precise file path):

Requires: mvn(jline:jline) >= 2.10