Date: Fri, 10 May 2002 10:09:36 -0700 From: "Andrew Gerweck" <andrew.gerweck@presedia.com> To: <java@FreeBSD.ORG> Subject: RE: Request for review: Standardising Java library directory locations Message-ID: <JKEAICMFONIKJINBOEKLOEENCLAA.andrew.gerweck@presedia.com> In-Reply-To: <200205100920.58261.mcclain@looneys.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I think that it's really the porter's job to handle this. Perhaps something roughly like this could help. * Maintain a jar packaging list that maps all the ports' jar files to the classes they install. A pkg-classlist might be a reasonable requirement on ports that install jars. * A simple tool could then scan a developer's port to make sure that the jars installed don't have any class conflicts with a port that owns that jar. jarlint? * If there's a conflict, one port can be chosen the official bearer of the jar. This may require a new port if there's no winner. * If an application actually requires an old jar, it can install it into a separate folder, which keeps version names. /usr/lib/share/java/classes/compat/ or something like it. The central storage is a great thing for Java developers. Most developers just want to build up a single directory of jars and suck all its files into their classpath. As long as we can keep things running smoothly for applications, I'm all for the central directory. Thanks, Andy -----Original Message----- From: owner-freebsd-java@FreeBSD.ORG [mailto:owner-freebsd-java@FreeBSD.ORG]On Behalf Of Mcclain Looney Sent: Friday, May 10, 2002 7:21 AM To: java@FreeBSD.ORG Subject: Re: Request for review: Standardising Java library directory locations I'm not sure a centralized storage model for libraries is such a good idea. It's been my experience that many java apps are shipped with old, outdated or incompatible "support" jar files (old versions of xalan or some such). In addition to this, I've even seen jars shipped which contain the contents of 4 or five other jars inside (several of which were old)!. I'm afraid centralized storage of java libs might lead to a "jarfile hell" situation. Perhaps a versioned approach could be developed (similar to .so links). my $.02 cheers, -mcclain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?JKEAICMFONIKJINBOEKLOEENCLAA.andrew.gerweck>