[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722639#comment-16722639
]
Alex O'Ree commented on DERBY-6645:
-----------------------------------
if i'm understanding this correctly, the generator runs to add security
policies that must go in the derby jar file.
The 'build' folder needs at least one class from the derby jar file in order to
compile. I was able to work around this by bubbling up to class files into the
shared/commons module.
The security policy generation is a bit more complex. It appears to make a
classes and a generated folder. Generated needs to go into the derby jar, i
think. The "classes" folder looks like it is policy files for unit tests. Is
that right?
> 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)
