You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Davide Grandi (JIRA)" <ji...@apache.org> on 2019/05/09 20:36:00 UTC

[jira] [Updated] (DERBY-6645) Switch to Maven for building Apache Derby

     [ https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Grandi updated DERBY-6645:
---------------------------------
    Attachment: build2dot.zip

> 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, build2dot.zip
>
>
> 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)