Date: Fri, 5 Dec 2008 13:53:53 +0100 (CET) From: Lapo Luchini <lapo@lapo.it> To: FreeBSD-gnats-submit@FreeBSD.org Cc: Lapo Luchini <lapo@lapo.it> Subject: ports/129435: java/jakarta-commons-dbcp not BROKEN on jdk15 Message-ID: <200812051253.mB5CrrBe029548@deepie.home.lapo.it> Resent-Message-ID: <200812051300.mB5D01pg008802@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 129435 >Category: ports >Synopsis: java/jakarta-commons-dbcp not BROKEN on jdk15 >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: Fri Dec 05 13:00:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Lapo Luchini >Release: FreeBSD 7.1-PRERELEASE amd64 >Organization: >Environment: System: FreeBSD deepie.home.lapo.it 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #11: Sun Oct 19 15:29:12 CEST 2008 root@deepie.home.lapo.it:/usr/obj/usr/src/sys/DEEPIE amd64 >Description: java/jakarta-commons-dbcp is currently unconditionally BROKEN, but it seems to me to be working OK when using jdk15 (altough it might well be broken with jdk16). I see no way to "correct" the situation programmatically (it depends on the JVM that commons-collections was compiled with, not the JVM that this port was compiled with), but just for clarity we could maybe change BROKEN= does not build to BROKEN= does not build unless jakarta-commons-collections is compiled with jdk15 So that people using jdk15 know they can actually manually delete the BROKEN line and have a working port. >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?200812051253.mB5CrrBe029548>