Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <4915975.175641280991856736.JavaMail.jira@thor>
Date: Thu, 5 Aug 2010 03:04:16 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4715) Write jvm information and path of
 derby.jar to derby.log
In-Reply-To: <11111040.60211277480930634.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan commented on DERBY-4715:
----------------------------------------

Thanks, Lily.

You only get an email from Hudson if something goes wrong with the build. As you can see here [1], it didn't find any problems with your backport to 10.6.
The job is checking the repos hourly, and the job itself is quickly done, so if you introduce a build break (or a JavaDoc warning) you should get an email within one and a half hour or so.

Another tip when merging a single revision is to use svn merge -c REV instead of svn merge -r  REV-1:REV.


[1] http://hudson.zones.apache.org/hudson/job/Derby-branch-10.6/23/

> 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.