Add a port of jakarta-commons-discovery.

The Discovery Component is about discovering, or finding, implementations for
pluggable interfaces. It provides facilities intantiating classes in general,
and for lifecycle management of singleton (factory) classes.

Fundamentally, Discovery locates classes that implement a given Java interface.
The discovery pattern, though not necessarily this package, is used in many
projects including JAXP (SaxParserFactory and others) and commons-logging
(LogFactory). By extracting this pattern, other projects can (re)use it and
take advantage of improvements to the pattern as Discovery evolves.

Discovery improves over previous implementations by establishing facilities for
working within managed environments. These allow configuration and property
overrides without appealing to the global System properties (which are scoped
across an entire JVM).

PR:		65490
Submitted by:	Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
This commit is contained in:
Greg Lewis 2004-04-18 06:18:19 +00:00
parent 99b8b64f4d
commit b97389634f
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=107393
4 changed files with 67 additions and 0 deletions

View file

@ -39,6 +39,7 @@
SUBDIR += jakarta-commons-cli
SUBDIR += jakarta-commons-collections
SUBDIR += jakarta-commons-dbcp
SUBDIR += jakarta-commons-discovery
SUBDIR += jakarta-commons-lang
SUBDIR += jakarta-commons-logging
SUBDIR += jakarta-commons-pool

View file

@ -0,0 +1,48 @@
# New ports collection makefile for: jakarta-commons-discovery
# Date created: 2004-04-13
# Whom: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
#
# $FreeBSD$
#
PORTNAME= commons-discovery
PORTVERSION= 0.2
CATEGORIES= java devel
MASTER_SITES= ${MASTER_SITE_APACHE_JAKARTA}
MASTER_SITE_SUBDIR= ${PORTNAME:S,-,/,}/binaries
PKGNAMEPREFIX= jakarta-
MAINTAINER= herve.quiroz@esil.univ-mrs.fr
COMMENT= A Java library for locating resources (including classes)
USE_JAVA= YES
JAVA_VERSION= 1.3+
JAVA_RUN= JDK
NO_BUILD= YES
.if !defined(NOPORTDOCS)
PORTDOCS= api LICENSE
.endif
JARFILE= ${PORTNAME}.jar
PLIST_FILES+= ${JAVAJARDIR:S,^${PREFIX}/,,}/${JARFILE}
post-extract:
@${MV} ${WRKSRC}/LICENSE ${WRKSRC}/docs/
do-install:
@${ECHO_MSG} -n ">> Installing JAR as ${JAVAJARDIR}/${JARFILE}..."
@${MKDIR} ${JAVAJARDIR}
@${INSTALL_DATA} ${WRKSRC}/${JARFILE} ${JAVAJARDIR}/
@${ECHO_MSG} " [ DONE ]"
.if !defined(NOPORTDOCS)
@${ECHO_MSG} -n ">> Installing documentation..."
@${MKDIR} ${DOCSDIR}
.for DOCFILE in ${PORTDOCS}
@${CP} -r ${WRKSRC}/docs/${DOCFILE} ${DOCSDIR}/
@${ECHO_MSG} -n " ${DOCFILE}"
.endfor
@${CHOWN} -h -R ${SHAREOWN}:${SHAREGRP} ${DOCSDIR}
@${ECHO_MSG} " [ DONE ]"
.endif
.include <bsd.port.mk>

View file

@ -0,0 +1,2 @@
MD5 (commons-discovery-0.2.tar.gz) = 2273f5f83a477f4f18fccf3a00e2b48c
SIZE (commons-discovery-0.2.tar.gz) = 118701

View file

@ -0,0 +1,16 @@
The Discovery Component is about discovering, or finding, implementations for
pluggable interfaces. It provides facilities intantiating classes in general,
and for lifecycle management of singleton (factory) classes.
Fundamentally, Discovery locates classes that implement a given Java interface.
The discovery pattern, though not necessarily this package, is used in many
projects including JAXP (SaxParserFactory and others) and commons-logging
(LogFactory). By extracting this pattern, other projects can (re)use it and
take advantage of improvements to the pattern as Discovery evolves.
Discovery improves over previous implementations by establishing facilities for
working within managed environments. These allow configuration and property
overrides without appealing to the global System properties (which are scoped
across an entire JVM).
WWW: http://jakarta.apache.org/commons/discovery/