Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@www.apache.org Received: (qmail 72162 invoked from network); 22 Aug 2004 19:00:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Aug 2004 19:00:18 -0000 Received: (qmail 12982 invoked by uid 500); 22 Aug 2004 19:00:16 -0000 Delivered-To: apmail-jakarta-jetspeed-dev-archive@jakarta.apache.org Received: (qmail 12858 invoked by uid 500); 22 Aug 2004 19:00:15 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 12838 invoked by uid 99); 22 Aug 2004 19:00:14 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [66.163.169.226] (HELO smtp106.mail.sc5.yahoo.com) (66.163.169.226) by apache.org (qpsmtpd/0.27.1) with SMTP; Sun, 22 Aug 2004 12:00:12 -0700 Received: from unknown (HELO ?192.168.1.5?) (david?jencks@66.93.38.137 with plain) by smtp106.mail.sc5.yahoo.com with SMTP; 22 Aug 2004 19:00:11 -0000 Mime-Version: 1.0 (Apple Message framework v613) Content-Transfer-Encoding: 7bit Message-Id: <7C983F51-F46D-11D8-9D84-000D93361CAA@apache.org> Content-Type: text/plain; charset=US-ASCII; format=flowed To: jetspeed-dev@jakarta.apache.org From: David Jencks Subject: jetspeed 2 build organization suggestions Date: Sun, 22 Aug 2004 12:00:08 -0700 X-Mailer: Apple Mail (2.613) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I have been reviewing the jetspeed 2 build process and believe it could be improved in several areas. 1. using maven features appropriately within the current project structure. For instance, it appears to me that using the multiproject plugin instead of the reactor can replace about 236 lines with 2 in the top level maven.xml file. 2. restructuring the project to eliminate conditionals and clarify dependencies. Currently the build appears to be oriented entirely toward deploying on tomcat, and from my brief review this appears to permeate many areas of the project. I suggest removing all such dependencies from current build files and creating a new set of modules for each installation environment, installation/tomcat installation/weblogic installation/geronimo ... that will customize as appropriate for the target environment and provide appropriate installation tools. Similarly, I think it might be advisable to factor out the database setup support into separate modules such as installation/database/hsqldb installation/database/oracle ... I have not yet discovered to what extent the persistence support is pluggable, but if for instance you are using ojb via its jdo support the choice of jdo vendor and appropriate setup could also be isolated in separate modules. I'd like to know if there are objections to this approach before I spend a significant amount of time experimenting with it. Many thanks, david jencks --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org