incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Castagna (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-191) Jena module structure and build
Date Thu, 19 Jan 2012 08:09:41 GMT


Paolo Castagna commented on JENA-191:

Any23 is currently using Sesame, ANY23-19 lists the classes they are using from Sesame.
When I asked why Sesame was chosen the answer included: Maven artifact (at the time Jena did
not have those) and size (in bytes) (this is still the case).
Any23 is a small project and probably they want as little and as small dependencies as possible
(but you could/should ask them directly about this).
Any23 might be interested in the jena-core module which is one of the modules listed above:
it will have Maven artifacts and it will be much smaller than the current "Jena".
This is why JENA-191 is "related" to ANY23-19.
> 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