Build failed

I'm setting up an EC2 instance following the "Installing OM2.x On Ubuntu64 - Headlessv2 - v12.10" guide. Everything up to Step 9 works with no errors, until: /usr/adm/apache-ant-1.8.4/bin/ant -Ddb=mysql The build fails with this: :: [ivy:resolve

Re: Build failed

Unfortunately mentioned libraries were removed from Red5 repository You need to use 2.1 or download binary distribution of 2.0 On Mon, Jan 21, 2013 at 6:04 PM, Matthew wrote: > I'm setting up an EC2 instance following the "Installing OM2.x On Ubuntu64 > - Headlessv2 - v12.10" guide. Everything u

some questions to recordings and different moodle-sites

Hello, I've some questions about openmeetings in connection with different moodle-installations. I have installations of openmeetings (1.8, 1.9 and 2.0) for different moodle-sites. Particularly I am interested in how to manage conference-recordings of openmeetings. The goal is to have one openmeet

RE: Build failed

If you are wanting to build 2.1 the latest (Not 2.0) then use this SVN command instead: svn checkout https://svn.apache.org/repos/asf/incubator/openmeetings/trunk/singlewebapp/ From: Rene' Rosenbaum [mailto

RE: Build failed

And pre compiled 2.0 is here: https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/lastSuccessfulBuild/artifact/2.0/dist/apache-openmeetings-incubating-2.0.0.r1383872-12-09-2012_1009.tar.gz From: Stephen Cottham [mailto:stephen.cott...@robertbird.com.au] Sent:

Re: Build failed

Hi, great ... I actually installed the pre-compiled version already! Runs well, thanks to all the contributors! Now, I want to install and compile the sources in order to modify OM for my purposes. As I don't know how well v2.1 runs already, I decided to stick to

Re: some questions to recordings and different moodle-sites

lots of questions :) 1) openmeetingsModuleKey should be used to separate users/files of multiple CMS connected to one openmeetings (multiple moodles in your case) 2) sure you can manage the recordings it is located at OM_HOME/webapps/openmeetings/streams/hibernate/ 3) The id in the streams folder

Re: Build failed

you can try to take a look a build.xml from 2.1 it has code to patch ivy.xml and ivysettings.xml of red5 to fix this issues. On Mon, Jan 21, 2013 at 10:34 PM, Rene' Rosenbaum wrote: > Hi, > great ... I actually installed the pre-compiled version already! Runs > well, thanks to all the contrib

Re: Build failed

Dear Maxim, thanks, will have a look! However, this issue is probably of broad interest. Any further suggestions or locations within the build file that point to a solution are highly appreciated. Will summarize my findings afterwards to make them available to the

RE: Build failed

The Debian guide has been updated to show SVN download and build for 2.1, Step 9a has the pre-compiled 2.0 steps. The other updates will have to wait till later tomorrow. Best Regards From: Rene' Rosenbaum [mailto:r...@meecoda.de] Sent: 21 January 2013 15:59 To: openmeetings-use

Re: Build failed

you need code from build.xml line 880 and line 992 + build-red5_ivy.xsl build-red5_ivysettings.xsl from 2.1 I see no need merge this back into 2.0. I believe should be used as binary distribution :) On Mon, Jan 21, 2013 at 11:00 PM, Stephen Cottham < stephen.cott...@robertbird.com.au> wrote: >

Re: Build failed

Hi Maxim, good point ... however, v20 is the latest stable release and only version available via the homepage. Any build using the current setup will fail. Probably worth the hassle especially considering the fact that OM is now a Tier 1 Apache project. Tha

Re: Build failed

you will need to copy build-red5_ivy.xsl build-red5_ivysettings.xsl from 2.1 to 2.0 and merge the build.xml file (around lines 880 and 992) On Mon, Jan 21, 2013 at 11:27 PM, Rene' Rosenbaum wrote: > Hi Maxim, > good point ... however, v20 is the latest stable release and only version > avai

Re: some questions to recordings and different moodle-sites

Regarding releasing, I think a first step towards that would be to decide on a release manager and about the features that need to be completed for 2.1. I guess we all have a rough idea about what should go into v2.1 but no concrete consens was made yet IMHO. Sebastian 2013/1/22 Maxim Solodovnik

Features that need to be completed for 2.1

Please consider: One feature to include in 2.1 would be enabling Adobe's Acoustic Echo Cancelling (AEC). We have tested this, and it greatly improves end user experience for meetings (for people whose computers do not support hardware AEC). Thanks, George Kirkham From: seba.wa

Re: Features that need to be completed for 2.1

I see currently two main things: - getting all changes done needed for the clustering + test them - create backups of current and previous OpenMeetings versions and import them (it would be great if the import could be automized using a JUnit test, so that with any future change when can simply r

RE: Features that need to be completed for 2.1

Sebastian, You only see two main points, not three? : ( Thanks, George Kirkham : ) thanks heaps for your efforts, Sebastian, we all appreciate it. From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] Sent: Tuesday, 22 January 2013 3:27 PM To: openmeetings-

Re: Features that need to be completed for 2.1

I actually just contributed something to your thread. So at the discussion list would be now: - AEC feature - cluster features - backup import / JUnit test for import there is neither a decision made nor a closing of the list. So potentially new things could be added too. Also any opinion about