after building updated OM is available in /singlewebapp/dist/red5 (you
can run it)
in case of flash changes you can leave red5 running and just reload the
browser
On Tue, Apr 2, 2013 at 2:15 PM, Andun Sameera andun...@gmail.com wrote:
Hi Maxim,
I think there is small problem in
The background for my question was this. I have worked with products
are built on top of OSGi. There are lot of java packages loaded to run
the product. When we do a change in one of those packages what we did
was building the particular package and replacing the jar file in the
distribution. Not
sure, same here:
1) build using ant (all components)
2) run from dist/red5
3) make changes
4) rebuild debug client only
5) reload browser
in case of java changes:
1) build using ant (all components)
2) run from dist/red5
3) make changes
4) rebuild ant jar.only
5) restart from dist/red5
6) reload
Hi Devs,
Currently I am looking at the
https://issues.apache.org/jira/browse/OPENMEETINGS-507. I have gone
through the code and found some suspicious place where this bug lies.
To work further more I need some help,
-The normal way of building OM is via the ant script. Say I have done
a little
