[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722534#comment-16722534
]
Rick Hillegas commented on DERBY-6645:
--------------------------------------
Mavenizing the build should be much easier now that Derby has been converted
into JPMS modules via the work on DERBY-6945. At a high level, you will need a
pom for each of the child directories of trunk/java, most of which correspond
to production modules. It should be straightforward to convert the build.xml
scripts in those directories into poms.
The devil will be in details such as making sure that the top level pom fires
off child poms in the correct order.
I recently revamped how we generate security policies. That work is tracked by
DERBY-3547. The policy files are described by
trunk/java/org.apache.derby.engine/org/apache/derby/security/securityPolicies.xml.
They are generated by the build tool
trunk/java/build/org/apache/derbyBuild/SecurityPolicyGenerator.java, which runs
when the top level build.xml script calls its generateSecurityPolicies target.
I think that "mojo" is the name for the maven equivalent of an ant build tool.
> 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)
