The package description for JBoss4 is out of date, incorrect and needs to be corrected.
State Changed From-To: open->feedback jboss4@menelaos [11:47:45]> portlint WARN: /usr/ports/java/jboss4/pkg-descr exceeds 24 lines, make it shorter if possible.(currently 26 lines) WARN: Makefile [50]: whitespace before end of line.
Responsible Changed From-To: freebsd-ports-bugs->vs I'll do this
Responsible Changed From-To: vs->hq I'll handle this. With the patch applied, portlint says the following: WARN: /home/rv/src/ports/java/jboss4/pkg-descr exceeds 24 lines, make it shorter if possible.(currently 26 lines) Could you resubmit something shorter? I'll add the 'devel' category while we are here.
Responsible Changed From-To: hq->vs Hi Volker, I'm sorry, you took the PR beetween the time I getpr and the time I take-pr, which has been at most 1 minute long... The PR is yours again, now, and the pointyhat is mine :) Herve.
On Fri, Jan 21, 2005 at 10:48:33AM +0000, Volker Stolz wrote: > Synopsis: update java/jboss4 package description. > > State-Changed-From-To: open->feedback > State-Changed-By: vs > State-Changed-When: Fri Jan 21 10:48:00 GMT 2005 > State-Changed-Why: > jboss4@menelaos [11:47:45]> portlint > WARN: /usr/ports/java/jboss4/pkg-descr exceeds 24 lines, make it shorter if possible.(currently 26 lines) > WARN: Makefile [50]: whitespace before end of line. Below is patch which fixes both warnings. -- Jonathan Chen <jonc@chen.org.nz> ---------------------------------------------------------------------- When all else fails, RTFM diff -ruN /usr/ports/java/jboss4/Makefile ./Makefile --- /usr/ports/java/jboss4/Makefile Wed Jan 12 17:47:27 2005 +++ ./Makefile Sat Jan 22 08:40:06 2005 @@ -47,7 +47,7 @@ AUTO_START?= NO STOP_TIMEOUT?= 5 PID_FILE= /var/run/${APP_SHORTNAME}.pid -JAVA_OPTS= +JAVA_OPTS= JAVA_CP= bin/run.jar:${JAVA_HOME}/lib/tools.jar JAVA_MAIN= org.jboss.Main DAEMONCTL_DIR= ${FILESDIR} diff -ruN /usr/ports/java/jboss4/pkg-descr ./pkg-descr --- /usr/ports/java/jboss4/pkg-descr Sat Apr 27 09:54:15 2002 +++ ./pkg-descr Sat Jan 22 08:39:24 2005 @@ -1,24 +1,24 @@ -JBoss is an implementation of the EJB 1.1 (and parts of 2.0) specification, -that is, it is a server and container for Enterprise JavaBeans. In this it -is similar to Sun's 'J2SDK Enterprise Edition' (J2EE), but the JBoss core -server provides only an EJB server. The JBoss core does not include a web -container for servlets/JSP pages, although there are bundles available that -include either Tomcat or Jetty. The minimal core offering means that JBoss -has minimal memory and disk space requirements. JBoss will run very -effectively on a machine with 64 megabytes of RAM, and requires only a few -megabytes of disk (including source code!). Sun's J2EE requires a minimum of -128 megabytes of RAM, and 31 megabytes of disk space. Because of its small -memory footprint, JBoss starts up about 10 times faster than J2EE. There is -a built-in SQL database server for handling persistent beans, and this -starts up automatically with the server (J2EE ships with the CloudScape SQL -server, which has to be started separately). +JBoss AS 4 is an officially certified J2EE 1.4 application server. The +certification guarantees that JBoss AS 4 conforms to the formal J2EE +specification. -One of the nicest features of JBoss is its support for `hot' deployment. What -this means is that deploying a Bean is a simple as copying its JAR file into -the deployment directory. If this is done while the Bean is already loaded, -JBoss automatically unloads it, then loads the new version. Contrast this -with the rigmarole that other J2EE server makes us go through... JBoss is -distributed under the LGPL, which means that it's free, even for commercial -work, and the LGPL ensures that it remains that way. +- supports J2EE Web Services including JAX-RPC (Java API for XML for +Remote Procedure Call) and the Web Services for J2EE Architecture. + +- implements the JMS (Java Messaging Service) 1.1 specification. + +- implements the JCA (Java Connector Architecture) 1.5 specification. +The JCA 1.5 specification adds support for the life cycle management of +resource adapters, worker thread management as well as transaction and +message inflow from the resource adapter to the application server. + +- implements the Java Authorization Contract for Containers (JACC) +specification. + +- implements the EJB 2.1 specification. The EJB 2.1 specification +extends the message-driven bean contracts to support other messaging +types in addition to JMS. It supports stateless session beans as web +service endpoints. It also includes a new container managed service +called the EJB timer service. WWW: http://www.jboss.org/
State Changed From-To: feedback->closed Committed, thanks!