incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Dickinson (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-191) Jena module structure and build
Date Tue, 10 Jan 2012 13:20:39 GMT


Ian Dickinson commented on JENA-191:

Looks like a reasonable repackaging to me. Some quick points:

* Why does -iri need to be separate, not in -commons? Does anything else re-use it?

* Inference engines: in -api, or separate? It's fairly big, iirc

* I'd like to have a place to build up a collection of examples, and we proposed jena-examples
as a peer of -core, etc, but I haven't got around to creating it. I'd still like to have it
in there somewhere.

> Jena module structure and build
> -------------------------------
>                 Key: JENA-191
>                 URL:
>             Project: 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