[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726826#comment-16726826
]
Bryan Pendleton commented on DERBY-6645:
----------------------------------------
It would be great if some of this wonderful information could end up in the
Derby Wiki.
Or perhaps, even if just the Derby Wiki had a few pointers back here.
Or maybe it belongs in a beefed up BUILDING.html ?
In the meantime, thanks Alex and Rick for the great discussion, since the Derby
build procedures have evolved somewhat over the last year or two and it's good
to get these details out on the table.
> 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)
