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 Thu, 03 Jul 2014 12:23:25 GMT

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

Rick Hillegas commented on DERBY-6645:

Hi Moritz,

Can you explain more about the difficulties you encountered when building Derby? Your feedback
will help us improve the build instructions here: http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
Did you have trouble building Derby via the command line or under an IDE (if so, which one)?

The active Derby contributors don't use Maven much. So I don't think that the active contributors
are likely to convert the Ant scripts to Maven. That work would have to be done by a new contributor.


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