[
https://issues.apache.org/jira/browse/DERBY-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895429#action_12895429
]
Lily Wei commented on DERBY-4715:
---------------------------------
Thanks Kristian for reviewing the merge code. After 'ant clobber all buildjars'
and 'ant javadoc', suites.All and derbyall test suites are passing. I did some
tests against ibm jvm for this merge. I commit the merge to 10.5 and 10.6
branches.
I hope Hudson build will pick up the changelist. I did not get emails after
commit my code. I hope not receiving emails will not delay me to react to any
issue cause by my commit. However, I know you guys are always watching too.
Please let me know if there is anything I should pay attention to.
The wiki-page is very helpful. Thank you. I shall add any new information as I
discover them. The new svn is 982370(10.6) and 982401(10.5).
> Write jvm information and path of derby.jar to derby.log
> --------------------------------------------------------
>
> Key: DERBY-4715
> URL: https://issues.apache.org/jira/browse/DERBY-4715
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.6.1.0
> Reporter: Lily Wei
> Assignee: Lily Wei
> Priority: Minor
> Fix For: 10.7.0.0
>
> Attachments: DERBY-4715-1.diff, DERBY-4715-10.5_967304.diff,
> DERBY-4715-10.6_967304.diff, DERBY-4715-2.diff, DERBY-4715-3.diff,
> DERBY-4715-4.diff, DERBY-4715-5.diff, DERBY-4715-6.diff, DERBY-4715-7.diff,
> DERBY-4715-8.diff, derby.log
>
>
> The bug is part of DERBY-1272. In production environment, derby.jar can be
> located different than the derbyclient.jar It can be easier if we have jvm
> version information and path of derby.jar are in the derby.log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
