because of some JMF logs I looked into the whole JMF stuff a bit.
My question is: which jmf is used when I call "ant run". Actually
there are two jmf.jar in the classpath when I call "ant run". One
jmf.jar is in "lib/installer-exclude/jmf.jar" and appears first in the
CP, the second one is in "lib/os-specific/linux/installer-exclude/jmf.jar".
AFAIK (I may err here) there is also a jmf.jar somewhere in the bundles.
So - which one of the JMFs is really used?
Of course, the two jmf.jar in the classpath are different. They contain
the same classes but they are often from different date, the class files
have different sizes etc.
Could this lead to problems in the overall media handling? There a some
problems in media handling AFAIK.
because of some JMF logs I looked into the whole JMF stuff a bit.
My question is: which jmf is used when I call "ant run". Actually
there are two jmf.jar in the classpath when I call "ant run". One
jmf.jar is in "lib/installer-exclude/jmf.jar" and appears first in the
CP, the second one is in "lib/os-specific/linux/installer-exclude/jmf.jar".
IIRC we use all OS specific jmf.jar-s and bundle them together with the
media implementation in corresponding media.jar-s. We create one
media.jar per OS (see sc-bundles/os-specific).
When you run the project, the ant "run" target tries to detect which
system we are running on and then copies the corresponding media.jar in
sc-bundles. This is the media.jar, and hence jmf.jar, that get's loaded
by felix. All the others are ignored even though they may be in the
class path (kudos to felix).
AFAIK (I may err here) there is also a jmf.jar somewhere in the bundles.
Nah, that's all
Hope this helps.
Cheers
Emil
···
So - which one of the JMFs is really used?
Of course, the two jmf.jar in the classpath are different. They contain
the same classes but they are often from different date, the class files
have different sizes etc.
Could this lead to problems in the overall media handling? There a some
problems in media handling AFAIK.
