I was asked to make sure that tanukiwrapper and libreadline-java were up
to date for F10.


What I found is that there is no consistent policy for either .so
location or .jar location for Java packages in Fedora. Here are some
examples:


Library location:

eclipse: /usr/lib64/eclipse
jss: /usr/lib64
libreadline-java: /usr/lib64/libreadline-java
tanukiwrapper: /usr/lib64

Jar location:

eclipse: /usr/lib64/java
jss: /usr/lib/java
libreadline-java: /usr/lib64/libreadline-java
tanukiwrapper: /usr/share/java

I believe that libreadline-java was meant to be the model for the JNI
policy, but the problem is that jpackage-utils (build-classpath) does
not seem to be updated to work with the new jar location. NB: I tested
on F9, so if this has changed, let me know.


We have very little time to do anything about this before the F10
freeze, so I suggest we take the path of least-resistance, e.g., we have
to move libreadline-java back since we would not be able to update all
the packages and the tools and make sure that they work in time for F10.


--
Sincerely,

David Walluck
<david@zarb.org>

--
fedora-devel-java-list mailing list
fedora-devel-java-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list

David Walluck <david@zarb.org> writes:

> I was asked to make sure that tanukiwrapper and libreadline-java were
> up to date for F10.
>
> What I found is that there is no consistent policy for either .so
> location or .jar location for Java packages in Fedora.

There is a policy:

https://fedoraproject.org/wiki/Packaging/Java#Packaging_JAR_files_that_use_JNI

but some existing packages may not follow it.

> Here are some examples:
>
> Library location:
>
> eclipse: /usr/lib64/eclipse

Eclipse is a special case. Andrew Overholt can comment on this.

> jss: /usr/lib64
> libreadline-java: /usr/lib64/libreadline-java
> tanukiwrapper: /usr/lib64
>
> Jar location:
>
> eclipse: /usr/lib64/java
> jss: /usr/lib/java
> libreadline-java: /usr/lib64/libreadline-java
> tanukiwrapper: /usr/share/java

Ideally jss and tanukiwrapper would be updated to follow the packaging
guidelines.

> I believe that libreadline-java was meant to be the model for the JNI
> policy, but the problem is that jpackage-utils (build-classpath) does
> not seem to be updated to work with the new jar location.

What is the symptom of this problem?

> NB: I tested on F9, so if this has changed, let me know.
>
> We have very little time to do anything about this before the F10
> freeze, so I suggest we take the path of least-resistance, e.g., we
> have to move libreadline-java back

I'm not sure what you mean by this.

> since we would not be able to update all the packages and the tools
> and make sure that they work in time for F10.

Tom

--
fedora-devel-java-list mailing list
fedora-devel-java-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list

* David Walluck <david@zarb.org> [2008-10-15 13:33]:
> What I found is that there is no consistent policy for either .so
> location or .jar location for Java packages in Fedora. Here are some
> examples:

The guidelines have locations.

http://fedoraproject.org/wiki/Packaging/Java#Directory_structure
http://fedoraproject.org/wiki/Packaging/Java#Packaging_JAR_files_that_use_JNI

Perhaps the packages you were looking at just didn't meet the guidelines
(I will say that Eclipse doesn't count since it's not a "regular" java
app in that its plugin jars -- and few .sos -- aren't really/easily
usable by other java apps).

Andrew

--
fedora-devel-java-list mailing list
fedora-devel-java-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list

Thomas Fitzsimmons wrote:

What is the symptom of this problem?


If each jar is to be stored in its own directory, then build-classpath
and build-jar-repository need to be updated to be able to find these jar
locations. Otherwise, we just just get


$ build-classpath libreadline-java
/usr/bin/build-classpath: error: Could not find libreadline-java Java
extension for this JVM


/usr/bin/build-classpath: error: Some specified jars were not found

The other issue is that someone has to be willing to find and update all
JNI packages to the new policy.


I am not sure whye clipse should be a special case. There are quite a
few desktop applications (tuxguitar, vuze) that could make use of swt.


--
Sincerely,

David Walluck
<david@zarb.org>

--
fedora-devel-java-list mailing list
fedora-devel-java-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list