[jira] [Commented] (JENA-191) Jena module structure and build

["Bruno P. Kinoshita (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523063#comment-14523063 ] 

Bruno P. Kinoshita commented on JENA-191:
-----------------------------------------

[~andy.seaborne] I believe this issue can be closed. The project has already a structure and getting even better for Jena3 :-) WDYT?

> Jena module structure and build
> -------------------------------
>
>                 Key: JENA-191
>                 URL: https://issues.apache.org/jira/browse/JENA-191
>             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 was sent by Atlassian JIRA
(v6.3.4#6332)