[ https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Moritz Hoffmann updated DERBY-6645: ----------------------------------- Attachment: DERBY-6645_v1.patch I was able to build most of Derby using Maven. There are still some issues: * jars are built without resources. I need to figure out where localization properties etc. come from - any hints are appreciated! * Most tests fail because jars get built without resources * Eclipse plug-ins are not yet built Attached there is a patch [^DERBY-6645_v1.patch] that shows my current efforts. > 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 > 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 (v6.2#6252)