openmeetings-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Solodovnik <solomax...@gmail.com>
Subject Re: When doing the upgrade, can I just copy and paste the binary files?
Date Tue, 03 Feb 2015 03:04:11 GMT
It might work in case there were no DB changes between releases. But I
would recommended to perform backup/restore and to use latest OM available
(3.0.4 will hopefully be released this week)

WBR, Maxim
(from mobile, sorry for the typos)
On Feb 3, 2015 6:15 AM, "Wentao Liu" <cscmucmm@aliyun.com> wrote:

> Hello,
>
> When I am doing the upgrade from OM 2.0 to 2.1, can I just copy and paste
> the binary files? I am using the same databases.
>
> Thanks,
> Wentao
>
> -----Original Message-----
> From: Wentao Liu [mailto:cscmucmm@aliyun.com]
> Sent: Monday, February 02, 2015 10:24 PM
> To: dev@openmeetings.apache.org
> Subject: RE: Can anybody help use ant or mvn to compile applicaton
>
> Hello,
>
> For 3.0.X, I will use ant 1.9.2 or 1.9.3 to compile and for 2.x I will
> give up for any modification..
>
> Thanks
>
> -----Original Message-----
> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> Sent: Monday, February 02, 2015 12:06 PM
> To: dev
> Subject: Re: Can anybody help use ant or mvn to compile applicaton
>
> Hello,
>
> for 3.0.x you should use ant to compile, "cannot extract tar.gz file" error
> most probably caused by ant 1.9.4, please use 1.9.2 or 1.9.3
>
> 2.x is not compilable due to it is too old, some libraries were moved from
> it's original places ....
>
> On Sat, Jan 31, 2015 at 7:15 PM, Wentao Liu <cscmucmm@aliyun.com> wrote:
>
> > Hello guys,
> >
> > Can anybody help to use ant or mvn to compile application? I followed the
> > method on project homepage to compile a OM 3.0.x file on windows platform
> > which was downloaded via svn but got errors like "cannot extract tar.gz
> > file" so I think I should compile and run on Linux platform, please
> confirm.
> >
> > Further, I compiled a 2.0 incubator version on windows via ant but got
> > errors like "no dependency" which I think the build.xml file is so older
> > that some dependency files were removed, please confirm.
> >
> > Thanks,
> > Wentao
> >
> > -----Original Message-----
> > From: Maxim Solodovnik [mailto:solomax666@gmail.com]
> > Sent: Saturday, January 31, 2015 11:35 AM
> > To: dev
> > Subject: Fwd: Wicket WebRTC Integration
> >
> > JFYI
> >
> > ---------- Forwarded message ----------
> > From: Zala Pierre GOUPIL <goupilpierre@gmail.com>
> > Date: Sat, Jan 31, 2015 at 5:49 AM
> > Subject: Re: Wicket WebRTC Integration
> > To: users@wicket.apache.org
> >
> >
> > Hi,
> >
> > Excellent work, congrats! And I'm talking about all your
> > "wicket-components-playground" project! I'll test your Wicket WebRTC
> > Integration and tell you how it goes.
> >
> > In fact, I'm currently using a full JS WebRTC component (
> > https://code.google.com/p/webrtc4all/) but I'm not fully satisfied with
> > it.
> > Hopefully, yours will do it for me.
> >
> > Regards,
> >
> > Pierre
> >
> >
> >
> >
> > On Fri, Jan 30, 2015 at 5:26 PM, Tobias Soloschenko <
> > tobiassoloschenko@googlemail.com> wrote:
> >
> > > Hi everybody,
> > >
> > > I just implemented a component to provide a way to integrate a video
> > > conference to Wicket applications using WebRTC - I would be very
> pleased
> > to
> > > receive feedback!
> > >
> > > An installation of NodeJS is required.
> > >
> > > https://github.com/klopfdreh/wicket-components-playground
> > >
> > > (Scroll to section "Wicket WebRTC Integration")
> > >
> > > kind regards
> > >
> > > Tobias
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> >
> > --
> > Si le sang ne coule pas assez chaud dans tes veines, je le répandrai sur
> le
> > sable pour qu'il bouille au soleil.
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
> >
>
>
> --
> WBR
> Maxim aka solomax
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message