db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6645) Switch to Maven for building Apache Derby
Date Fri, 21 Dec 2018 15:12:00 GMT

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

Rick Hillegas commented on DERBY-6645:

1) messages.xml contains the source for the English engine and client messages. It is pre-processed
by MessageBuilder (as described in my previous comment). MessageBuilder writes the English
messages (engine and client) into trunk/generated/java/org.apache.derby.engine/org/apache/derby/loc/messages_en.properties.
The source for the non-English engine and client messages lives in locale-specific message
files in the source tree of the engine module (in the trunk/java/org.apache.derby.engine/org/apache/derby/loc/messages_$locale.properties
files). The splitmessages program processes trunk/generated/java/org.apache.derby.engine/org/apache/derby/loc/messages_en.properties
and trunk/java/org.apache.derby.engine/org/apache/derby/loc/messages_*.properties, separating
out the client messages into their own properties files and splitting the engine messages
into smaller chunks as described in my previous comment. This happens both for the English
and the non-English messages.

2) English and non-English source for the tools messages live in the source tree for the tools
module, in trunk/java/org.apache.derby.tools/org/apache/derby/loc. The English messages are
simply copied into the classes directory of the tools module. The non-English messages are
copied into the locale-specific directory trees by the build script for the tools module (trunk/java/org.apache.derby.tools/build.xml).

3) The source for the server messages lives in locale-specific properties files in trunk/java/org.apache.derby.server/org/apache/derby/loc/drda,
that is, in the source tree for the server module. These files are copied into the classes
tree for the server module.

> Switch to Maven for building Apache Derby
> -----------------------------------------
>                 Key: DERBY-6645
>                 URL: https://issues.apache.org/jira/browse/DERBY-6645
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Moritz Hoffmann
>            Priority: Major
>         Attachments: DERBY-6645_v1.patch
> For a new user building Derby is very hard. It does not follow established Java project
structures and requires a lot of prior knowledge. Also the documentation is rather short.
Especially running the tests is non-intuitive at the beginning. Thus, I propose that Derby
switches to building using Maven and restructures its components in a cleaner way. Testing
should be revised to produce reproducible results. This would make development and testing
much easier and more user-friendly.

This message was sent by Atlassian JIRA

View raw message