db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4715) Write jvm information and path of derby.jar to derby.log
Date Wed, 04 Aug 2010 18:21:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895349#action_12895349

Kristian Waagan commented on DERBY-4715:

If the fix merged cleanly (svn merge succeeded), and you were able to do a clean build and
ran the tests without (new) errors, you can basically commit.
I prefer to do a clean build to make sure all changes are picked up; I run 'ant clobber all
buildjars'. In some rare cases you can also introduce JavaDoc errors by doing a backport,
so it doesn't hurt to run the JavaDoc target either. For the newer branches this will be picked
up by the Hudson build jobs, and a mail will be sent to derby-dev (plus the committer(s) who
introduced the change(s)).

You may have seen this already, but there are some guidelines at http://wiki.apache.org/db-derby/MoveAChangeBetweenBranches
>From a quick glance, it seems you can save yourself some time by not posting patches if
the merge is clean :)
The wiki-page seems to be rather up to date, but I think there are a few issues there that
would benefit from a refresh.

> 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:
>            Reporter: Lily Wei
>            Assignee: Lily Wei
>            Priority: Minor
>             Fix For:
>         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.

View raw message