Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Tue, 10 Jan 2012 11:20:39 +0000 (UTC)
From: "Andy Seaborne (Created) (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: 
 <1078743602.25110.1326194439183.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (JENA-191) Jena module structure and build
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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