using old SVN as long as there is no new

[seba....@gmail.com]

Hi Maxim,

I think it is save to commit changes to the old SVN @GoogleCode at the moment.
The new SVN at Apache is not yet ready and it might take a bit more.
Alexei did request to stop committing to the GoogleCode SVN because he
made a dump of it. This dump won't be used by Apache folks as they
can't import it.
They will need to make a fresh copy.

We will need to test the result anyway ... eventually we will need to
commit things twice.

Sebastian

--
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba....@gmail.com

[Maxim Solodovnik]

OK

Thanks :)
I'm investigating 1.9 issue right now

and will not commit until I finish 

--
WBR
Maxim aka solomax

[Maxim Solodovnik]

Hello Sebastian,

I seems to fix the 1.9 issue

will wait a little bit more (need more than 1 positive feedback)

then commit fix into SVN.

[Maxim Solodovnik]

Hello Sebastian,

Seems the fix works as expected

I have checked correct jar into SVN (both 1.9 branch and trunk)

could you please make 1.9.1?

[seba....@gmail.com]

okay,

I will pack a new release today and upload it to GoogleCode.

btw: What was the exact root cause? I think it was again the javax.persistance.* that was in the java-ee.5-1-2.jar that we have removed in an earlier version ? When updating the red5 server we accidently forgotten to replace that jar ?

Thanks!
Sebastian

2011/12/13 Maxim Solodovnik <solom...@gmail.com>

[Maxim Solodovnik]

Yes.

Somehow javax.persistense.* classes are conflicted only on some machines.

I forget to modify  java-ee.5-1-2.jar while updating red5 version

my bad