Bug 923282 - eclipse-dtp: JAR files are installed into wrong directories
Summary: eclipse-dtp: JAR files are installed into wrong directories
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-dtp
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 923270
TreeView+ depends on / blocked
 
Reported: 2013-03-19 15:27 UTC by Mikolaj Izdebski
Modified: 2013-03-19 15:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-19 15:58:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mikolaj Izdebski 2013-03-19 15:27:43 UTC
Description of problem:
eclipse-dtp package is installing JAR files into wrong locations.

According to Java packaging guidelines[1] all architecture-independent
JAR files MUST go into %{_javadir} or a Java-version specific
directory %{_javadir}-* as appropriate and JAR files using JNI or
containing JNI shared objects themselves MUST be placed in %{_jnidir}.
eclipse-dtp package violates that guidelines by installing
JAR files into other directories.

If JAR were put into some non-standard directory for technical reasons
then these JARs should be moved to proper locations (as described in the
guidelines[1]) and symbolic links can be placed in the previous location.

I am not going to attach the full list of JAR files,
but this list can be obtained using repoquery:

  repoquery --repoid rawhide -l eclipse-dtp | grep '\.jar$' | grep -v /usr/share/java | grep -v /usr/lib/java

Version-Release number of selected component (if applicable):
1.10.2-1

Additional info:
[1] http://fedoraproject.org/wiki/Packaging:Java
[2] http://fedoraproject.org/wiki/Packaging:Guidelines

Comment 1 Mikolaj Izdebski 2013-03-19 15:58:39 UTC
I was not aware that the separate Eclipse guidelines was officially
approved packaging guidelines. See comment in bug#923270 for more details.

Because of the above I am closing this bug now.


Note You need to log in before you can comment on or make changes to this bug.