Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Aug 2004 18:18:12 +0200 (CEST)
From:      Herve Quiroz <hq@FreeBSD.org>
To:        FreeBSD-gnats-submit@FreeBSD.org
Cc:        Greg Lewis <glewis@FreeBSD.org>
Subject:   ports/70219: Updating Java ports to bsd.java.mk 2.0
Message-ID:  <200408091618.i79GICMd015114@arabica.esil.univ-mrs.fr>
Resent-Message-ID: <200408091620.i79GKKiA024668@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         70219
>Category:       ports
>Synopsis:       Updating Java ports to bsd.java.mk 2.0
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 09 16:20:20 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Herve Quiroz
>Release:        FreeBSD 5.2.1-RELEASE-p9 i386
>Organization:
>Environment:

5.2.1-RELEASE-p9 i386

>Description:

bsd.java.mk 2.0 has been up for quite some time now and although it provides
backward compatibility with 1.0, I believe it is now time to update Java ports
so they are 2.0 compliant.

This PR is mostly a reminder for ports commiters (and a TODO list for me). I
encourage ports commiters to enforce (or request from the submitters)
bsd.java.mk 2.0 compliance for any new port or port update PR. I will take care
of the remaining ports.

You'll find a lot of information regarding bsd.java.mk 2.0 in the Porter's
handbook [1] but feel free to email me directly if you require any further
information on the subject or assistance in migrating a given port.

This is still to be verified but I believe bsd.java.mk backward compatibility
will cause trouble if the port is not fully 2.0 compliant or 1.0 compliant. So
port migration should be done at once or not at all. That's one the reasons why
I would really want to get rid of backward compatibility ASAP.

I would have written a quick migration guide but given the above issue, it
could mislead porters. Basically, if the only bsd.java.mk trigger you are using
is USE_JAVA, here is the migration procedure:

# with bsd.java.mk 1.0
USE_JAVA=	<required JDK version>

# with bsd.java.mk 2.0
USE_JAVA=	yes
JAVA_VERSION=	<required JDK version>

Beware though that doing so will probably prevent any 1.0-only macro (e.g.
NO_BUILD_DEPENDS_JAVA) to have any effect on the port.

As mentioned in 1.0, you may check bsd.java.mk support using the 'java-debug'
make target that is automatically provided as long as USE_JAVA is defined
(whether the port is 1.0 or 2.0 compliant).


So far, the concerned ports are the following ones:

- archivers/jzip.org
- audio/jxm
- audio/musiccontrol
- benchmarks/scimark2
- comms/java-commapi
- databases/arcexplorer
- databases/erserver
- databases/postgis-jdbc
- databases/postgresql-jdbc
- devel/antlr
- devel/apache-ant
- devel/argouml
- devel/colorer
- devel/itext
- devel/jude_take
- devel/smc
- devel/swarm
- dns/crossip
- editors/jedit
- editors/jedit-devel
- french/geonext
- ftp/dmachine
- ftp/jftp
- games/cgoban2
- games/dmjava
- games/jtans
- games/robocode
- german/geonext
- graphics/aoi
- graphics/batik
- graphics/jpatch
- graphics/tintfu
- irc/pircbot
- java/avalon-logkit
- java/bluej
- java/bsh
- java/bugseeker
- java/bugseeker-demo
- java/cos
- java/cryptix-jce
- java/forte
- java/gj
- java/gj-jdk11
- java/gnu-regexp
- java/j2sdkee13
- java/jaf
- java/jai
- java/jai-imageio
- java/jakarta-bcel
- java/jakarta-commons-beanutils
- java/jakarta-commons-lang
- java/jakarta-commons-pool
- java/jakarta-commons-primitives
- java/jakarta-log4j
- java/jakarta-struts
- java/jasmin
- java/java-checkstyle
- java/java-cup
- java/java-getopt
- java/java3d
- java/javamail
- java/jaxen
- java/jboss2
- java/jboss3
- java/jce-aba
- java/jdbcpool
- java/jflex
- java/jlex
- java/jmf
- java/jode
- java/jsdk
- java/jump
- java/junit
- java/netbeans
- java/netcomponents
- java/netrexx
- java/poseidon
- java/proguard
- java/xdoclet
- lang/jython
- lang/kawa
- lang/linux-j
- lang/starlogo
- math/vtk-java
- net/apache-soap
- net/danamics
- net/edonkey-gui-java
- net/freenet
- net/frost
- net/java-beepcore
- net/ldapbrowser
- net/limewire
- net/phex
- net/xnap
- net-mgmt/airport
- net-mgmt/confregdecode
- science/ovt
- sysutils/jdiskreport
- textproc/ant-xinclude-task
- textproc/denature
- textproc/dtd2relax
- textproc/dtdinst
- textproc/fop
- textproc/javacc
- textproc/jing
- textproc/ppower4
- textproc/smartdoc
- textproc/smartdoc-devel
- textproc/trang
- textproc/xalan-j
- textproc/xincluder
- textproc/xmlenc
- textproc/xmlpull
- textproc/xt
- www/apache-forrest
- www/apache-jserv
- www/axis
- www/jakarta-jmeter
- www/jakarta-tomcat3
- www/jakarta-tomcat4
- www/jakarta-tomcat41
- www/jetty
- www/resin2
- www/resin3

--> 124 ports


[1] Porter's handbook - Using Java
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-java.html

>How-To-Repeat:
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408091618.i79GICMd015114>