[
https://issues.apache.org/jira/browse/JENA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183295#comment-13183295
]
Andy Seaborne commented on JENA-191:
------------------------------------
jena-examples - good idea. They should definitely be part of the build. How
should deliver them? JENA-190
Inference engines - happy to separate out.
jena-iri - merely because its a reasonable sized, self-contained thing. People
have used on it's own but we don't really highlight as an independent library
so much now due to the time needed. It does have it's own way of doing tests
built from XML IIRC. It uses jflex to build the parser/lexer but we run that
separately and only use the generated code in the build proper.
> 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
