A good place to hang out but I'm not sure what it has to do w/ YOKO-37.
Regards,
Alan
Kresten Krab Thorup wrote, On 3/6/2006 11:25 AM:
how about joining an IRC channel, I suggest
irc://irc.freenode.net:6667/yoko
Kresten Krab Thorup
[EMAIL PROTECTED]
On Mar 6, 2006, at 8:02 PM, Sakala, Adinarayana wrote:
Hi Alan,
Kresten has already committed the work related to his task.
Infact, he actually closed the task, I reopened it because some more
work on top of kresten's work needs to be done.
What prasad is in addition to what kresten has committed.
I think it probably makes sense to close YOKO-37 task as kresten has
completed the initial work and create new one for
prasad's work.
If this is ok i will do that and assign it to prasad.
thanks,
adi
-----Original Message-----
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: Monday, March 06, 2006 12:44 PM
To: [email protected]
Subject: Re: Initial tasks
Prasad,
Kresten is already working on this. Why would you re-assign this to
yourself?
Regards,
Alan
Kosuru, Prasadarao wrote, On 3/6/2006 8:23 AM:
Hi Kresten,
I am currently working on build framework using maven2. Also
I'll rename
the folder 'orb' to 'core', and once I get a working copy will modify
the trunk accordingly (assuming that I get root password by
that time).
So I'll re-assign the task YOKO-37 to my name.
Let know if you have any comments on this.
Regards,
Prasad
-----Original Message-----
From: Kresten Krab Thorup [mailto:[EMAIL PROTECTED]
Sent: 06 March 2006 08:10
To: Sakala, Adinarayana
Cc: [email protected]
Subject: Re: Initial tasks
On Mar 3, 2006, at 6:46 PM, Sakala, Adinarayana wrote:
How about if we identify the modules that we can think of now?
Looking at prasad's and your proposal we atleast have five
modules to
start with,
tools, core, rmi, system_tests, distribution Each of the
module will
be a maven2 subproject which will build a
yoko-<module-name>-1.0-SNAPSHOT
If the above list and names sound good to you, prasad and everybody
lets go with implementing that project strucutre.
This looks fine; I think it's perfect to call the base system
"org.apache.yoko.core" in stead of "org.apache.yoko.orb".
Also, i dont see a need for generated-java directories.
Thats just a redudant thing from IONA's internal build system.
we can just have main/org/apache/yoko/orb etc.
I like keeping the generated source separate so that when we
one day get
an IDL compiler, then we can generate all this properly. It would be
nice to eventually go there.
thanks,
Adi Sakala
-----Original Message-----
From: Kresten Krab Thorup [mailto:[EMAIL PROTECTED]
Sent: Friday, March 03, 2006 8:01 AM
To: Alan D. Cabrera; Sakala, Adinarayana;
[email protected]
Subject: Initial tasks
For some reason I'm not on yoko-dev. Sorry, but anders
just made me
aware that there has been a discussion going on over the project
structure.
I have no intention of forcing structure to be something specific,
but I am eager to get started on the other things that depend on
having the structure decided.
The structure that is in there now is as lised below, and I have
reorganized the class spaces com.ooc -> org.apache.yoko.orb.
trunk/orb [ all of the base orb from IONA ]
src/main/
java
generated-java
src/test
java
generated-java
The pom builds an artifact named yoko-orb-1.0-SNAPSHOT
The unit tests need some reworking to be able to run in this new
environment. What's in there is not JUnit; perhaps we can
retrofit
the tests to use JUnit somehow.
I added the extra "orb" at the end of the package name
(org.apache.yoko.orb), because it would make a lot of
sense to have
additional modules (all the corba services) in separate
yoko modules.
Also, I am thinking that there should be a parallel module
(trunk/rmi) for the RMI/ValueHandle implementation that
would build
yoko-rmi-1.0-SNAPSHOT. This really is a separate thing,
and people
can choose to use this one or whatever comes with the JDK.
Alan, can you have me added to the mailing list?
Kresten Krab Thorup
[EMAIL PROTECTED]
