db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1376) File java/engine/org/apache/derby/loc/messages_en.properties - Message XSLAT.D
Date Tue, 06 Jun 2006 22:10:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1376?page=comments#action_12415060 ] 

David Van Couvering commented on DERBY-1376:

I like Halley's recommendation, but I would suggest that providing the format Halley suggests
may be difficult given our current message framework (that is, provide a message with multiple
lines).  It might be sufficient to say

Log directory {0} exists.   The directory may belong to another database.  Please make sure
the specified logDevice location is correct. 

(I do like to say "please", it doesn't hurt to be polite to our users).

Also, it would be helpful to say *where* you specify logDevice (e.g. "please make sure the
derby.foo.logDevice property is set to the correct location.")


> File java/engine/org/apache/derby/loc/messages_en.properties - Message XSLAT.D
> ------------------------------------------------------------------------------
>          Key: DERBY-1376
>          URL: http://issues.apache.org/jira/browse/DERBY-1376
>      Project: Derby
>         Type: Improvement

>   Components: Localization
>     Versions:
>  Environment: Text for exceptions
>     Reporter: Halley Pacheco de Oliveira
>     Priority: Minor
>      Fix For:

> The message XSLAT.D (String LOG_SEGMENT_EXIST = "XSLAT.D";) states:
> XSLAT.D=Log directory {0} exists. Please make sure specified logDevice location is correct.
> But it seems by the source code that the problem is not that this directory exists, but
the fact that it is not empty (// make sure log directory is empty, in LogToFile.java). So
it seems to me that the following message would be better:
> XSLAT.D=Log directory {0} is not empty. Please make sure specified logDevice location
is correct.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message