db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6645) Switch to Maven for building Apache Derby
Date Fri, 21 Dec 2018 16:48:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726888#comment-16726888

Alex O'Ree commented on DERBY-6645:

WRT localization files:
 # Any thoughts on just including all of the resource files for all languages in the main
jar files? I would probably make things simpler long run but any one using derby would probably
have to update their build scripts/pom/gradle files and whatnot. I know there was some discussion
on static footprints, however i always thought that the resource loader would only load the
resource files for the current locale, not all of them ( or am i misunderstanding something?).
I'm a bit hesitant to make this change now as the branch isn't quite working and there's already
a lot of changes and I have no idea if this will ever be merged as is. I'm already a few days
into this and i have no idea how much longer it will take


A few more questions:
 # what's the difference between a "sane" build and an "insane" build? I've rigged this up
for maven profiles at the moment. So `mvn clean install -Pinsane` with 'sane' being the default.
Hoping that this configuration is good enough.
 # what documentation outputs does the ant based build provide? Javadocs, website? pdf? etc.
How are the non-javadoc items produced and is there any interest in having maven's reporting
functions do some or all of the heavy lifting for this?


Side note: Of the changes on my branch, it's primarily moving stuff around and converting
the build script automation. Long term, there probably should be some additional cleanup of
the code base. There's a bunch of classes with lowercase names and some packages with upper
case letters, both of which shouldn't be. Test classes should be probably housed with the
module that's being testing, if possible. Sounds like a problem for another day.

> 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:
>            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

View raw message