[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723517#comment-16723517
]
Alex O'Ree commented on DERBY-6645:
-----------------------------------
i'm not a fan of mixing up production and test resources. They shouldn't both
end up in the release jar correct? Is there a way I can tell the difference
with the template policies files or a simply way i can redirect them to a
different output folder?
As of right now, I have the 'build' project producing a jar, which is called by
maven exec plugin during the build of the 'engine' folder. I'm starting to
think that a straight up maven plugin may be easier to work with in this case.
In either situation, i need to know which is which.
> 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)
