Hi Wonseok,
All the changes from trunk has already been ported to V2.1 branch. Here
is the
fisheye
link for the commit.
Development for V3 is happening in svn repository. As I mentioned in
the previous mail, cvs trunk for V2 is dead. Current active development
for V2 is happening in
V2.1
branch. Any critical bug in entity-persistence should be checked
into V2.1 branch.
Let me know if you have more questions.
Thanks,
Mitesh
Wonseok Kim wrote:
Hi Mitesh,
Then I'm curious how we continue to work on others bugs which won't
make it to 2.1?
Is there another entity-persistence source in V3 repository? Where is
the real trunk?
I also can see other check-ins into the trunk like below. Then what do
those changes mean?
http://fisheye5.cenqua.com/changelog/~br=MAIN/glassfish/
Sorry, I'm not fully aware of recent situations of repository change
and I'm confused so please shed light on us!
Thanks
-Wonseok
On Jan 19, 2008 9:06 AM, Mitesh Meswani
<
Mitesh.Meswani@sun.com>
wrote:
Hi
Tom,
Trunk for v2 is dead. There are not builds/releases planned out of
trunk. Infect, it might not be in state to build any more.
I think you should try to get the checkin into V2.1. You can send Harry
a note on why this change is essential and impact of the change to get a
approval.
Thanks,
Mitesh
Tom Ware wrote:
> Issue number: 4016
> Obtained from: TopLink
> Submitted by: Tom Ware
> Reviewed by: Chris Delahunt
>
> Fix is in TopLinkClassWeaver
>
> Added test:
>
oracle.toplink.essentials.testing.tests.cmp3.fieldaccess.relationships.UniAndBiDirectionalMappingTestSuite.weavingEagerAndLazyRelationshipsTest
()
>
>
> Tested with entity-persistence-tests and oracle-internal tests
>
> Only checked into the trunk, so no target milestone set because I
am
> not sure what the milestone after 2.1 will be.