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 Tue, 18 Dec 2018 01:46:00 GMT

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

Rick Hillegas commented on DERBY-6645:
--------------------------------------

I'm afraid I'm not following you. Each module has its own source tree, its own generated source
tree, and its own classes tree. It seems to me that the test module is very clearly separated
from the production modules. Tests live in their own package space and are not bundled into
the production jars. Maybe what is puzzling from a maven viewpoint is the fact that there
is only one test module and not one apiece for each production 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: 10.10.2.0
>            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
(v7.6.3#76005)

Mime
View raw message