aboutsummaryrefslogtreecommitdiff
path: root/java/jakarta-commons-discovery
Commit message (Collapse)AuthorAgeFilesLines
* - Update to 0.4 [1]Herve Quiroz2007-02-102-13/+9
| | | | | | | | | | - Remove unneeded flag JAVA_RUN=JDK - Release maintainership Reported by: portscout [1] Notes: svn path=/head/; revision=184819
* SHA256ifyEdwin Groothuis2006-01-221-0/+1
| | | | | | | Approved by: krion@ Notes: svn path=/head/; revision=154157
* - Don't mkdir ${JAVAJARDIR} (already in mtree)Herve Quiroz2005-07-291-8/+3
| | | | | | | | - Use %%JAVAJARDIR%% - Use FIND | INSTALL_DATA rather than CP Notes: svn path=/head/; revision=140394
* Use my FreeBSD address in MAINTAINERHerve Quiroz2004-10-231-1/+1
| | | | Notes: svn path=/head/; revision=119982
* Add a port of jakarta-commons-discovery.Greg Lewis2004-04-183-0/+66
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> Notes: svn path=/head/; revision=107393