incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-191) Jena module structure and build
Date Thu, 19 Jan 2012 10:05:40 GMT


Andy Seaborne commented on JENA-191:

Have ANY23 a plan that might include ANY23-19?  If so, let's help - otherwise I don't think
we should design the module structure based on a "maybe".  If it turns into a concrete set
of requirements we can engage with then great but at the moment, the discussion seems to be
discussion.  It would be interesting if they have any useful input to Jena design.
> 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