From owner-freebsd-java Mon Feb 18 17:27: 2 2002 Delivered-To: freebsd-java@freebsd.org Received: from hotmail.com (f121.law8.hotmail.com [216.33.241.121]) by hub.freebsd.org (Postfix) with ESMTP id 81EA737B402 for ; Mon, 18 Feb 2002 17:26:58 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 18 Feb 2002 17:26:58 -0800 Received: from 63.196.107.131 by lw8fd.law8.hotmail.msn.com with HTTP; Tue, 19 Feb 2002 01:26:58 GMT X-Originating-IP: [63.196.107.131] From: "Tim Schafer" To: freebsd-java@freebsd.org Subject: Re: building jboss port question Date: Mon, 18 Feb 2002 17:26:58 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 19 Feb 2002 01:26:58.0433 (UTC) FILETIME=[860FEF10:01C1B8E4] Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I would suggest four ports: jboss jboss-tomcat3 jboss-tomcat4 jboss-jetty since this is the way JBoss binaries are distributed anyways making the port wrappers easy to maintain JBoss actually includes the respective product it's integrating with So these ports would be independant of the product being installed standalone >I was toying with JBoss, and writing a port - it makes sense to me >to keep the add-ons in their own ports, since they're standalone apps and >not part of JBoss as such. > I'd expect it to be a lot easier to not clobber someones >existing config >using this approach, as well. But I never got enough sense out of >the JBoss docs to see how it integrates other servers - partly because I >don't do an awful lot of EJB development... Tim Schafer tschafer@hotmail.com _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message