db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Moritz Hoffmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6645) Switch to Maven for building Apache Derby
Date Thu, 03 Jul 2014 12:49:25 GMT

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

Moritz Hoffmann commented on DERBY-6645:

Hi Rick,
thanks for replying! I came across the build instructions as well, and using them I was indeed
able to build the Derby jars. However, I had troubles loading it into Eclipse.

Eclipse tries to compile all Java files in the source directories. However, there are files
that only compile on a specific Java version, for example the JDBC implementation. The Ant
build avoids compiling those parts, but on Eclipse I cannot easily do that (have to exclude
every single source file from build if it depends on a requirement that my machine does not

I'm not saying these problems are unsolvable, but for new users such as me it would be much
easier to understand, test and develop Derby if it was following mentioned established structures.
I see your point that the build is working for active contributors and that there is no need
to change it and that a change in the build system might break things.

I see two approaches supporting Maven: Either change the directory structure to align with
the standard Maven layout, or try to gently convert the existing source to Maven modules by
adding pom files that are adapted to the current directory layout. The first option might
be (too) disruptive ;-)


> 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