Yes I think the Red5-Client SVN tree is rather newly updated.

However Paul Gregoire already updated it again.
The current mechanism for build the red5-client works like that:
Red5-Client needs the red5.jar from the red5-server build. So the ANT
script does build server first and then an "ant-copy" task copies the
red5.jar from the server to the client.
In the latest revision Paul seems to fix this issue by adding a dependency
to the red5-client ivy file (and making red5 available as archetype):
https://code.google.com/p/red5/source/detail?r=4381

I think we should do some tests now with red5 4380 and then release.
I will start a vote on that soon.

Sebastian

2012/6/14 Maxim Solodovnik <[email protected]>

> I tried to add dependency for red5 client same way we have server, but it
> was impossible since red5-client was not buildable by ant
>
>
> On Thu, Jun 14, 2012 at 10:42 AM, Maxim Solodovnik 
> <[email protected]>wrote:
>
>> Hello Sebastian,
>>
>> sorry for for the late response.
>> I'll check the build and will try to find the cause of this error.
>>
>> StreamProxy  forwards RTMP packets to some other server (like justin.tv)
>>
>>
>> On Wed, Jun 13, 2012 at 1:01 AM, [email protected] <
>> [email protected]> wrote:
>>
>>> I have fixed OPENMEETINGS-323.
>>> I have also done some changes to the red5-client.jar and the structure
>>> of our libraries.
>>> You will need to do a clean.all
>>> The structure is now:
>>> build/red5/server
>>> build/red5/client
>>>
>>> and both client as well as server can be configured in the
>>> build.properties to be different revisions (or the same).
>>> I have removed the dependency in the Ivy file to the red5-client-2.0.jar
>>> as we build it now locally and copy at the appropriate locations.
>>>
>>> The exception is gone, Screensharing does basically work again. But the
>>> RTMPTClient still can't connect. Same message like it was before: Handshake
>>> error/too long.
>>>
>>> BTW: What is this StreamProxy doing?
>>>
>>> Sebastian
>>>
>>> 2012/6/12 [email protected] <[email protected]>
>>>
>>> I've documentated progress in:
>>>> https://issues.apache.org/jira/browse/OPENMEETINGS-323
>>>>
>>>> Sebastian
>>>>
>>>> 2012/6/12 [email protected] <[email protected]>:
>>>> > Hi Maxim,
>>>> >
>>>> > after updating red5 to r4380 + enabling the RTMPT standalone in the
>>>> > jee-container.xml
>>>> > RTMPT did work locally (no chance yet to test it on a internet server)
>>>> >
>>>> > However the RTMPT-Screensharer does not startup at all.
>>>> > It throws an Exception:
>>>> > java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
>>>> >        at
>>>> org.red5.server.net.rtmp.BaseRTMPHandler.<clinit>(BaseRTMPHandler.java:62)
>>>> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> >        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>> Source)
>>>> >        at java.lang.reflect.Method.invoke(Unknown Source)
>>>> >        at com.sun.javaws.Launcher.executeApplication(Unknown Source)
>>>> >        at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
>>>> >        at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
>>>> >        at com.sun.javaws.Launcher.run(Unknown Source)
>>>> >        at java.lang.Thread.run(Unknown Source)
>>>> > Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
>>>> >        at java.net.URLClassLoader$1.run(Unknown Source)
>>>> >        at java.security.AccessController.doPrivileged(Native Method)
>>>> >        at java.net.URLClassLoader.findClass(Unknown Source)
>>>> >        at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
>>>> >        at java.lang.ClassLoader.loadClass(Unknown Source)
>>>> >        at java.lang.ClassLoader.loadClass(Unknown Source)
>>>> >        ... 10 more
>>>> >
>>>> > I think it might relate to changes done to Red5
>>>> > http://code.google.com/p/red5/source/detail?r=4377
>>>> >
>>>> > But I think we also need to update our Red5-Client to the latest
>>>> > revision instead of RC2.
>>>> >
>>>> > Sebastian
>>>> >
>>>> > --
>>>> > Sebastian Wagner
>>>> > https://twitter.com/#!/dead_lock
>>>> > http://www.openmeetings.de
>>>> > http://www.webbase-design.de
>>>> > http://www.wagner-sebastian.com
>>>> > [email protected]
>>>>
>>>>
>>>>
>>>> --
>>>> Sebastian Wagner
>>>> https://twitter.com/#!/dead_lock
>>>> http://www.openmeetings.de
>>>> http://www.webbase-design.de
>>>> http://www.wagner-sebastian.com
>>>> [email protected]
>>>>
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> https://twitter.com/#!/dead_lock
>>> http://www.openmeetings.de
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> [email protected]
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
[email protected]

Reply via email to