ports - FreeBSD ports tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	Bump portrevision due to upgrade of devel/gettext.	Edwin Groothuis	2008-06-06	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \|	The affected ports are the ones with gettext as a run-dependency according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT in Makefile (29 of them). PR: ports/124340 Submitted by: edwin@ Approved by: portmgr (pav) Notes: svn path=/head/; revision=214430
*	Apache Commons project are no longer hosted under MASTER_SITES_APACHE	Emanuel Haupt	2008-02-27	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \|	jakarta/commons subdirectory, they have been moved one directory up. Introduce MASTER_SITE_APACHE_COMMONS_SOURCE and adjust 22 ports accordingly. PR: 121041 Submitted by: Marcin Cieslak <saper@system.pl> Approved by: portmgr (linimon) Notes: svn path=/head/; revision=208004
*	- Welcome X.org 7.2 \o/.	Florent Thoumie	2007-05-19	1	-0/+1
\| \| \| \| \| \| \| \|	- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}. - Bump PORTREVISION for ports intalling files in ${X11BASE}. Notes: svn path=/head/; revision=191544
*	- Update to 0.4 [1]	Herve Quiroz	2007-02-10	2	-13/+9
\| \| \| \| \| \| \| \| \| \|	- Remove unneeded flag JAVA_RUN=JDK - Release maintainership Reported by: portscout [1] Notes: svn path=/head/; revision=184819
*	SHA256ify	Edwin Groothuis	2006-01-22	1	-0/+1
\| \| \| \| \| \| \|	Approved by: krion@ Notes: svn path=/head/; revision=154157
*	- Don't mkdir ${JAVAJARDIR} (already in mtree)	Herve Quiroz	2005-07-29	1	-8/+3
\| \| \| \| \| \| \| \|	- Use %%JAVAJARDIR%% - Use FIND \| INSTALL_DATA rather than CP Notes: svn path=/head/; revision=140394
*	Use my FreeBSD address in MAINTAINER	Herve Quiroz	2004-10-23	1	-1/+1
\| \| \| \|	Notes: svn path=/head/; revision=119982
*	Add a port of jakarta-commons-discovery.	Greg Lewis	2004-04-18	3	-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