[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725467#comment-16725467
]
Rick Hillegas commented on DERBY-6645:
--------------------------------------
* The first item in the list is the server policy file, which you can see is
generated into the classes directory tree corresponding to the server module.
That is the only policy file packaged inside the product jars. It ends up in
derbynet.jar.
* Most of the remaining items are test-specific policy files, which you can see
are generated into the classes directory tree corresponding to the testing
module. All of those policy files end up in derbyTesting.jar.
* At the end of the list are the template policy files and some dita source
pages for the Security Guide topic dealing with Java security. As you can see,
all of those items are generated into the generated source tree corresponding
to the engine module. The template policy files are put in the demo directory
tree of the lib distributions built by the release targets. The release targets
also copy the generated dita source into the documentation tree so that the
Security Guide will contain examples of the template policies.
The target locations of these items are declared in securityPolicies.xml in the
<output> elements nested under the <policy> elements.
> 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)
