Red Hat Bugzilla – Bug 1023736
JAR file should put into /usr/share/java/jline2/jline2.jar
Last modified: 2013-10-29 12:20:32 EDT
Created attachment 816519 [details]
Suggestion patch to solve the reported issue
ON Rawhide the JAR file should be in
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.
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.
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:
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.
(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
Small correction. It will be:
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