The FreeBSD Ports Archive

FreeBSD java : jakarta-commons-discovery

A Java library for locating resources (including classes)

 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).  

jakarta-commons-discovery history

v. 1.5
date: 2007/05/19 20:12:50;  author: flz;  state: Exp;  lines: +1 -0
- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.

v. 1.4
date: 2007/02/10 22:49:14;  author: hq;  state: Exp;  lines: +6 -10
- Update to 0.4 [1]
- Remove unneeded flag JAVA_RUN=JDK
- Release maintainership

Reported by:	portscout [1]

v. 1.3
date: 2005/07/29 12:36:08;  author: hq;  state: Exp;  lines: +3 -8
- Don't mkdir ${JAVAJARDIR} (already in mtree)
- Use %%JAVAJARDIR%%
- Use FIND | INSTALL_DATA rather than CP

v. 1.2
date: 2004/10/23 01:56:23;  author: hq;  state: Exp;  lines: +1 -1
Use my FreeBSD address in MAINTAINER

v. 1.1
date: 2004/04/18 06:18:19;  author: glewis;  state: Exp;
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 
=============================================================================


v. 1.5
date: 2007/05/19 20:12:50;  author: flz;  state: Exp;  lines: +1 -0
- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.

v. 1.4
date: 2007/02/10 22:49:14;  author: hq;  state: Exp;  lines: +6 -10
- Update to 0.4 [1]
- Remove unneeded flag JAVA_RUN=JDK
- Release maintainership

Reported by:	portscout [1]

v. 1.3
date: 2005/07/29 12:36:08;  author: hq;  state: Exp;  lines: +3 -8
- Don't mkdir ${JAVAJARDIR} (already in mtree)
- Use %%JAVAJARDIR%%
- Use FIND | INSTALL_DATA rather than CP

v. 1.2
date: 2004/10/23 01:56:23;  author: hq;  state: Exp;  lines: +1 -1
Use my FreeBSD address in MAINTAINER

v. 1.1
date: 2004/04/18 06:18:19;  author: glewis;  state: Exp;
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 
=============================================================================


v. 1.5
date: 2007/05/19 20:12:50;  author: flz;  state: Exp;  lines: +1 -0
- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.

v. 1.4
date: 2007/02/10 22:49:14;  author: hq;  state: Exp;  lines: +6 -10
- Update to 0.4 [1]
- Remove unneeded flag JAVA_RUN=JDK
- Release maintainership

Reported by:	portscout [1]

v. 1.3
date: 2005/07/29 12:36:08;  author: hq;  state: Exp;  lines: +3 -8
- Don't mkdir ${JAVAJARDIR} (already in mtree)
- Use %%JAVAJARDIR%%
- Use FIND | INSTALL_DATA rather than CP

v. 1.2
date: 2004/10/23 01:56:23;  author: hq;  state: Exp;  lines: +1 -1
Use my FreeBSD address in MAINTAINER

v. 1.1
date: 2004/04/18 06:18:19;  author: glewis;  state: Exp;
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 
=============================================================================