From owner-freebsd-java Sun Feb 17 6:23: 9 2002 Delivered-To: freebsd-java@freebsd.org Received: from shikima.mine.nu (pc1-card4-0-cust77.cdf.cable.ntl.com [62.252.49.77]) by hub.freebsd.org (Postfix) with ESMTP id 8BC0137B402 for ; Sun, 17 Feb 2002 06:23:04 -0800 (PST) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 16cSDV-0003Cy-00; Sun, 17 Feb 2002 14:23:01 +0000 Date: Sun, 17 Feb 2002 14:23:01 +0000 From: Rasputin To: Jesse McConnell Cc: java@freebsd.org Subject: Re: building jboss port question Message-ID: <20020217142301.A12281@shikima.mine.nu> Reply-To: Rasputin References: <20020216195006.A40959@gallup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020216195006.A40959@gallup.com>; from jesse@gallup.com on Sat, Feb 16, 2002 at 07:50:06PM -0600 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 * Jesse McConnell [020217 01:53]: > http://www.jboss.org > > I am building out the jboss ports and I wanted to ask the troops on here > a few questions. > > First off, if someone else is already doing this, please let me know. > > Since jboss can be intalled by itself or with Tomcat 3.2.3 or Tomcat > 4.0.1 or even Jetty 3.1.3_1 I am thinking about going one of two ways. > First would be to just warn the port user to specify > WITH_JAKARTA_TOMCAT_3, WITH_JAKARTÅ_TOMCAT_4 or WITH_JETTY. Jboss is > packaged so it is already configured to make use of them, which can be > kinda a pain so I figured the options should be available outside of the > other ports which offer those programs. The other option would be to go > like the apache port and offer three different ports, jboss, > jboss-tomcat (which allows you to choose 3 or 4), and jboss-jetty. 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... > The other question is which jdk should I make these go against. The > forte ones seems to use the linux-jdk one to build against..but I am > thinking I'll just attach a pkg-message that explains where to launch > the program from and to set the JAVA_HOME of the vm you want to > use...Any feelings one way or the other? This is coming back to bsd.java.mk again, but I can confirm that JBoss starts up under jdk13 native quire happily (using latest patchset) - though as I said I haven't done much more than look at the management interface in a browser... -- Good news. Ten weeks from Friday will be a pretty good day. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message