You can find Nightly Builds of the software at: https://builds.apache.org/view/M-R/view/OpenMeetings/
To build a binary release of OpenMeetings you need:
Get the source:
svn checkout https://svn.apache.org/repos/asf/openmeetings/application/branches/3.0.x
Run the command:
There is no need to compile the client additionally! The ant task does it all! You will find a directory dist that contains OpenMeetings and a red5-server.
To compile the client you can also use ant:
ant # compiles a complete package into the folder dist ant compile.laszlo.main # compiles the client into main.as3.swf10.swf and main.swf8.swf ant compile.laszlo.main.debug # compiles the debug-client into maindebug.as3.swf10.swf and maindebug.swf8.swf ant -Ddb=<name of DB> # will copy <name of DB>_persistense.xml to persistense.xml #(for ex. ant -Ddb=mysql will set mysql as default DB)
To compile just the openmeetings JAR file:
To run Junit tests using ANT see JUnitTesting
To develop or build OpenMeetings you checkout the source as Eclipse project. You need the Subclipse or Subversive Plugin for Eclipse. If you just need to change 3 lines of code then your probably better switch to How to build a distribution .
To develop OpenMeetings you need at least:
Advanced Users: Check out the Code from the Repository as a Java project into Eclipse.
To download the required JARs for building and developing OpenMeetings you need to run the ANT comand:
ant -Ddb=<your_DB> dist prepare-eclipse
After the ANT command you need to press F5 and rebuild the project from inside Eclipse
1) Start Eclipse
6) Add the URL
and click Finish
ant dist prepare-eclipse
see the first chapter about the ANT tasks to compile the code. You will find a directory called dist which contains a regular openmeetings including red5. You can then use the usual process like described at installation to run the code then.
When you want to develop only client side there are handy ANT tasks so that you only rebuild the SWFs, same for the Java side.
It also takes much less time if you do use MySQL as database then rebuilding the software and waiting for Apache Derby to set up the database everytime you did rebuild.
Working behind a proxy:
If you are sitting behind a proxy you should add some proxy settings
before starting the build process.
For Apache Ivy see: http://ant.apache.org/ivy/faq.html
For SVN Command Line Client (From CollabNet 1.7) see: https://ctf6latest.collab.net/internal-help/index.jsp?topic=/teamforge610/faq/client_proxy_settings.html