incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Allen (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-191) Jena module structure and build
Date Wed, 29 Feb 2012 20:49:57 GMT


Stephen Allen commented on JENA-191:

I like the proposed single trunk layout and module naming/capitalization normalization.  Being
able to checkout and build everything in one go is attractive.

Also like the idea of /trunk/pom.xml to drive everything.  If we have this, then do we need
a jena-top or jena-parent project?  Couldn't we just move those functions directly into the

> Jena module structure and build
> -------------------------------
>                 Key: JENA-191
>                 URL:
>             Project: Apache Jena
>          Issue Type: Brainstorming
>            Reporter: Andy Seaborne
> The current multi-trunk, multi-module, multi-version build is good for independent evolution
but bad for making a jena a single "thing".
> Maybe we should have a single trunk, multi-module, single source-release, single version
number build for Jena.
> There would be a single POM in the root directory that did a module build (this is not
the parent POM).
> Advantages:
> - The build is simpler
> Disadvantages:
> - Individual release of a module is harder.
> See also JENA-190 (delivery).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message