[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724189#comment-16724189
]
Rick Hillegas commented on DERBY-6645:
--------------------------------------
To answer your question about policy files:
* Template policy files are all generated into the generated source tree
(specifically into
trunk/generated/java/org.apache.derby.engine/org/apache/derby/security)
alongside corresponding webpages for the Derby Security Guide. That directory
is in the generated source tree for the engine module.
* Production policy files are generated into the classes directory tree for the
engine module.
* Test policy files are generated into the classes directory tree for the
testing module.
> 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)
