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

["Andy Seaborne (Commented) (JIRA)" <ji...@apache.org>]

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

Andy Seaborne commented on JENA-191:
------------------------------------

Simple version:

As currently except move RIOT to jena-core.
Split out atlas/jena shared as jena-commons

jena/trunk/pom.xml
jena/trunk/jena-top/pom.xml
jena/trunk/jena-iri/...
jena/trunk/jena-core/...

jena/trunk/pom.xml does a moudle build of jena-iri, jena-core, ...

jena-top is independently released as at the moment.

                
> Jena module structure and build
> -------------------------------
>
>                 Key: JENA-191
>                 URL: https://issues.apache.org/jira/browse/JENA-191
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira