Red5 Unable to Start Distribution.
Posted
by Iscariot
on Stack Overflow
See other posts from Stack Overflow
or by Iscariot
Published on 2010-06-05T19:28:41Z
Indexed on
2010/06/05
19:32 UTC
Read the original article
Hit count: 416
I have installed subclipse, Ant, IvyDE, Red5 Plugin for eclipse, All of the Environmental variables are set and the necessary elements have been added to the path.
I am attempting to create a Red5 Distribution by using eclipse, opening Build.xml right clicking dist [default] in the outline window and running as and selecting Ant Builder.
Eclipse says that the build is Successful. I first stop the Red5 Service, and then I attempt to run the build I create in eclipse it fails, below are the errors that display in the command prompt.
I was hoping someone else might have run into a similar issue before.
Starting Red5
Red5 root: C:/Users/Admin/workspace/temp/red5_server/dist
Configuation root: C:/Users/Admin/workspace/temp/red5_server/dist/conf
Setting temp directory to C:\Users\Admin\AppData\localLow
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
The import org.slf4j.bridge cannot be resolved
The import org.springframework.context.support.FileSystemXmlApplicationC
ontext cannot be resolved
SLF4JBridgeHandler cannot be resolved
FileSystemXmlApplicationContext cannot be resolved to a type
FileSystemXmlApplicationContext cannot be resolved to a type
at org.red5.server.Launcher.<init>(Launcher.java:25)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.red5.server.Bootstrap.bootStrap(Bootstrap.java:132)
at org.red5.server.Bootstrap.main(Bootstrap.java:50)
Press any key to continue . . .
© Stack Overflow or respective owner