Tim Ellison wrote:
Stefano Mazzocchi wrote:
Geir Magnusson Jr wrote:
Mikhail Fursov wrote:
Does it mean that BCEL will be a part of JRE? So we can have
problems with
different BCEL versions if two of them is in classpath..
Heh. I forgot about that. I was just thinking
Stefano Mazzocchi wrote:
Geir Magnusson Jr wrote:
Mikhail Fursov wrote:
Does it mean that BCEL will be a part of JRE? So we can have problems with
different BCEL versions if two of them is in classpath..
Heh. I forgot about that. I was just thinking about licensing terms.
I
BTW, Yoko also has javax.rmi and javax.rmi.CORBA implementations...
These implementations are requires Apache BCEL.
2006/7/25, Alexey Petrenko [EMAIL PROTECTED]:
2006/7/25, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
Yep, we can integrate it immediatly they put M1 jars to
Alexey Petrenko wrote:
BTW, Yoko also has javax.rmi and javax.rmi.CORBA implementations...
These implementations are requires Apache BCEL.
That's ok - BECL is Apache Licensed (and an Apache project)
2006/7/25, Alexey Petrenko [EMAIL PROTECTED]:
2006/7/25, Geir Magnusson Jr [EMAIL
Does it mean that BCEL will be a part of JRE? So we can have problems with
different BCEL versions if two of them is in classpath..
?
On 7/26/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Alexey Petrenko wrote:
BTW, Yoko also has javax.rmi and javax.rmi.CORBA implementations...
These
Mikhail Fursov wrote:
Does it mean that BCEL will be a part of JRE? So we can have problems with
different BCEL versions if two of them is in classpath..
Heh. I forgot about that. I was just thinking about licensing terms.
I assume we can simply treat things as local to the boot
Geir Magnusson Jr wrote:
Mikhail Fursov wrote:
Does it mean that BCEL will be a part of JRE? So we can have problems with
different BCEL versions if two of them is in classpath..
Heh. I forgot about that. I was just thinking about licensing terms.
I assume we can simply treat things
2006/7/22, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure. I thought that all the tests are at
the end so all the sources are built. But
Alexey Petrenko wrote:
2006/7/22, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure. I thought that all the tests are at
the end so
This is excellent news! So, how do we get it integrated? :)
geir
Alexey Petrenko wrote:
2006/7/18, Alexey Petrenko [EMAIL PROTECTED]:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko
Yoko guys are preparing M1 release... Probably they will put all jars
needed by us right after their M1 :)
It seems that we (I) should start discussion on Yoko dev list to make
Yoko compatible with 1.5. If it will not brake their plans. And make
some fixes for Yoko.
SY, Alexey
2006/7/25, Geir
Alexey Petrenko wrote:
Yoko guys are preparing M1 release... Probably they will put all jars
needed by us right after their M1 :)
It seems that we (I) should start discussion on Yoko dev list to make
Yoko compatible with 1.5. If it will not brake their plans. And make
some fixes for Yoko.
Alexey Petrenko wrote:
Yep, we can integrate it immediatly they put M1 jars to the site. Or
our guys can build it by themselves.
Ok - so the integration will be the same style as mx4j, right?
I'll prepare the list of the files which we need to implement in
Harmony for Yoko. If there is
2006/7/22, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure. I thought that all the tests are at
the end so all the sources are built. But
Alexey Petrenko wrote:
2006/7/22, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure. I thought that all the tests are at
the end so
2006/7/24, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
2006/7/22, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure.
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure. I thought that all the tests are at
the end so all the sources are built. But Yoko runs the tests after
building each module...
I reviewed Yoko bug
Alexey Petrenko wrote:
There are not much news to share...
First of all I realized that I did not completely build Yoko. My build
was failed with the test failure. I thought that all the tests are at
the end so all the sources are built. But Yoko runs the tests after
building each
So how goes the YOKO battle?
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5 specification.
So it looks like a good
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5 specification.
So it looks like a good candidate for using as CORBA for Harmony.
The only problem
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5 specification.
So it looks like a good candidate for using as CORBA
Tim Ellison wrote:
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5 specification.
So it looks like a good candidate
Alexey Petrenko wrote:
I'm planing to do the following things in nearest future:
1. Get the list of the not implemented classes in Yoko according to 1.5
spec.
2. Check that we have all the classes needed by Yoko in Harmony.
Thoughts? Comments?
First thing that would be nice is to try and
Geir Magnusson Jr wrote:
Tim Ellison wrote:
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5 specification.
So it looks
Tim Ellison wrote:
Geir Magnusson Jr wrote:
Yes, but we can always filter things out too. Not really an issue.
How would you do that? Assuming that Yoko actually needs that code to
do something.
Of course- my assumption is that this is extra, no core stuff.
geir
2006/7/18, Tim Ellison [EMAIL PROTECTED]:
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5 specification.
So it looks
2006/7/18, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
I'm planing to do the following things in nearest future:
1. Get the list of the not implemented classes in Yoko according to 1.5
spec.
2. Check that we have all the classes needed by Yoko in Harmony.
Thoughts?
Alexey Petrenko wrote:
2006/7/18, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
I'm planing to do the following things in nearest future:
1. Get the list of the not implemented classes in Yoko according to 1.5
spec.
2. Check that we have all the classes needed by Yoko in
Geir Magnusson Jr wrote:
Alexey Petrenko wrote:
2006/7/18, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
I'm planing to do the following things in nearest future:
1. Get the list of the not implemented classes in Yoko according to 1.5
spec.
2. Check that we have all the
Alexey Petrenko wrote:
2006/7/18, Tim Ellison [EMAIL PROTECTED]:
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko have almost all the
packages from the 1.5
2006/7/19, Tim Ellison [EMAIL PROTECTED]:
Alexey Petrenko wrote:
2006/7/18, Tim Ellison [EMAIL PROTECTED]:
Alexey Petrenko wrote:
Guys,
There is a CORBA implementation in Apache incubator named Yoko.
http://incubator.apache.org/yoko/
I've built and reviewed it... It seems that Yoko
Alexey Petrenko wrote:
Here is the list of org.omg packages from 1.5 spec:
org.omg.CORBA
org.omg.CORBA_2_3
org.omg.CORBA_2_3.portable
org.omg.CORBA.DynAnyPackage
org.omg.CORBA.ORBPackage
org.omg.CORBA.portable
org.omg.CORBA.TypeCodePackage
org.omg.CosNaming
Hmm... OK
2006/7/19, Geir Magnusson Jr [EMAIL PROTECTED]:
Alexey Petrenko wrote:
Here is the list of org.omg packages from 1.5 spec:
org.omg.CORBA
org.omg.CORBA_2_3
org.omg.CORBA_2_3.portable
org.omg.CORBA.DynAnyPackage
org.omg.CORBA.ORBPackage
org.omg.CORBA.portable
-Original Message-
From: Tim Ellison [mailto:[EMAIL PROTECTED]
Then we can work with yoko to get either a build distribution tailored
to our needs, and also help finish the things we need.
It seems that we need to start with this since Yoko has build system
based on Maven. So
Nathan Beyer wrote:
-Original Message-
From: Tim Ellison [mailto:[EMAIL PROTECTED]
Then we can work with yoko to get either a build distribution tailored
to our needs, and also help finish the things we need.
It seems that we need to start with this since Yoko has build system
35 matches
Mail list logo
