[
https://issues.apache.org/jira/browse/JENA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219427#comment-13219427
]
Paolo Castagna commented on JENA-191:
-------------------------------------
> Proposal for a first step:
> Move active modules from /Jena2/MOD/ to /trunk/jena-mod:
>
> /Jena2/IRI/trunk -> /trunk/jena-iri
> /Jena2/ARQ/trunk -> /trunk/jena-arq
> /Jena2/jena/trunk -> /trunk/jena-core
> /Jena2/TDB/trunk -> /trunk/jena-tdb
> /Jena2/Fuseki/trunk -> /trunk/jena-fuseki
> /Jena2/SDB/trunk -> /trunk/jena-sdb
> /Jena2/LARQ/trunk -> /trunk/jena-larq
> /Jena2/JenaTop/trunk -> /trunk/jena-top ?? jena-parent
> /Jena2/Examples/trunk -> /trunk/jena-examples
+1
This layout allows a single checkout and it allows to have a pom.xml in /trunk/
to drive things.
I prefer "parent", people often refers to it as the "parent" pom.xml (separate,
but relevant is version numbers...)
> This leaves these alone:
>
> /dist
> /site
> /Import
and
/Scratch ?
/Experimental ?
> 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 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
