Is class-path-in-manifest permitted when packaging a JAR file depending on a JNI-using JAR file?
Assuming*that foo1(/usr/foo1/foo1.so /usr/foo1/foo1.jar)**and foo2(/usr/foo2/foo2.so /usr/foo2/foo2.jar) are*arch-dependent packages, bar1(/use/share/java/bar1.jar) is noarch package, foo2 and bar1 depends on foo1, Is there some examples*for how to*hack foo2 and bar1 to meet the java package guideline?在2010-02-28*02:51:39，"Ville*Skyttä"*<ville.skytta@iki .fi>*写道：
>On*Saturday*27*February*2010,*Chen*Lei*wro te:
>>*I*realized*from
>>*https://fedoraproject.org/w/index.php?title=Packaging:Java&oldid=154023#Gu
>>*ideline*that**if*you*are*depending*on* a*JNI-using*JAR*file,*you'll*need*to
>>*add*it*manually*--*build-classpath*will*not*find*it.**Does*this*mea n*that
>>*I*can*add*the*JNI-using*JAR*file*to*the*class-path*in*MANIFEST.MF?
>
>No.**Among*other*usual*problems*with*manif est*classpaths,*that*would*make*your*
>jar*arch*dependent*and*it*could*no*longer *be*installed*in*/usr/share/java*
>which*would*then*cascade*into*packages*that *use*your*jar.
>
>What*you*should*look*into*doing*is*finding *out*whether*the*"java"*to*be*
>invoked*is*a*64-bit*or*32-bit*one,*and*add*/usr/lib64/some/thing.jar*or*
>/usr/lib/some/thing.jar*accordingly*as*appropriate*to*your *classpath.**I'm*not*
>sure*if*there*are*any*helpers*available*fo r*doing*that.
>--
>packaging*mailing*list
>packaging@lists.fedoraproject.org
>https://admin.fedoraproject.org/mailman/listinfo/packaging
--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
|
