[
https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727505#comment-16727505
]
Rick Hillegas commented on DERBY-6645:
--------------------------------------
I am committed to the longstanding goal of minimizing Derby's static footprint
so that embedded Derby remains an option on resource-constrained devices. I
agree that message building and message management are overly complex and could
be simplified. I would support regularizing the tools messages so that the
non-English localizations are bundled into derbytools.jar alongside the English
versions, as is done with the server and client messages. However, I would not
support bundling all localizations of all messages into the engine jar or any
change which bloated up the static footprint for embedded usage by speakers of
any language.
The ant-based build targets include full javadoc for all the modules as well as
an abbreviated javadoc which describes just Derby's public api. Instructions
for building the full javadoc can be found at
http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
Continuous-integration builds refresh the trunk's public api posted at
https://builds.apache.org/job/Derby-trunk/lastSuccessfulBuild/artifact/trunk/javadoc/publishedapi/overview-summary.html
The website and the user documentation have their own code repositories and ant
scripts. I regret the separation of the docs source from the code source, but
that decision was made a long time ago. Instructions for building the docs can
be found at https://wiki.apache.org/db-derby/DocumentationDevelopment.
I support the addition of maven scripts to help maven-enthusiasts make
day-to-day contributions. However, I think that little value would be added by
re-plumbing Derby's code structure just to support maven metaphors and
assumptions.
> 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)
