[jitsi-dev] [jitsi-videobridge] build JVB tag 594 using old jar


#1

Hi ,Maven is pulling the latest jar from the repository ,hence JVB 594 tag fails.
We are not aware of the specific version used in 594 tag.How we can get the jar used in the 594 tag. Thanks And Regards,
R Kannan


#2

Hi ,
We can able to build videobridge 594 successfully using maven but fails while executing . Please give your suggestion to resolve it.
PFA Following steps I used to build jvb

error logs
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:java (default-cli) on project jitsi-videobridge: An exception occured while executing the Java class. null: InvocationTargetException: Unresolved compilation problems:
[ERROR] DefaultStreamConnector cannot be resolved to a variable[ERROR] DefaultStreamConnector cannot be resolved to a variable[ERROR] -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:java (default-cli) on project jitsi-videobridge: An exception occured while executing the Java class. null at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. null at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:345) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 moreCaused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.Error: Unresolved compilation problems: DefaultStreamConnector cannot be resolved to a variable DefaultStreamConnector cannot be resolved to a variable
at org.jitsi.videobridge.Main.main(Main.java:178) ... 6 more[ERROR]
Note:exception from libjitsi - DefaultStreamConnector class.

Thanks And Regards,
R Kannan

jvbbuild.txt (2.88 KB)

···

From: Kannan Radha krishnan <rkannan26@ymail.com>
To: Jitsi Developers <dev@jitsi.org>
Sent: Friday, 8 January 2016 5:43 PM
Subject: [jitsi-dev] [jitsi-videobridge] build JVB tag 594 using old jar
  
Hi ,Maven is pulling the latest jar from the repository ,hence JVB 594 tag fails.
We are not aware of the specific version used in 594 tag.How we can get the jar used in the 594 tag. Thanks And Regards,
R Kannan