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 "Alex O'Ree (JIRA)" <ji...@apache.org> on 2018/12/15 23:35:00 UTC

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

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

Alex O'Ree commented on DERBY-6645:
-----------------------------------

i'm totally in support of this. i have a bunch of ideas for enhancing derby but i've been unable to get netbeans to open the project. Maven based projects are supported by pretty much every ide out there. Maybe i'll give this a shot

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