kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/mail/mime4j/Makefile

44 lines
1.2 KiB
Makefile
Raw Normal View History

Decommissioning java 1.5 (EOLed since October 2009): suppress any reference to JAVA_VERSION= 1.5+ (part2)
2012-12-10 14:18:28 +01:00
# Created by: Alex Dupre <ale@FreeBSD.org>
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
# $FreeBSD$
PORTNAME= mime4j
Update to 0.7.2 release.
2012-01-13 12:23:08 +01:00
PORTVERSION= 0.7.2
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
CATEGORIES= mail java
MASTER_SITES= ${MASTER_SITE_APACHE}
MASTER_SITE_SUBDIR= james/${PORTNAME}
DISTNAME= apache-${PORTNAME}-${PORTVERSION}-bin
MAINTAINER= ale@FreeBSD.org
COMMENT= A Java parser for e-mail message streams
RUN_DEPENDS= ${JAVAJARDIR}/commons-logging.jar:${PORTSDIR}/java/jakarta-commons-logging
- The proper acronym for Apache Software License 2 is really AL2 - Thanks to crees@ for generating the initial patch PR: ports/163521 Submitted by: Pedro Giffuni <pfg apache.org> Hat: portmgr Exp run by: pav
2012-01-09 16:41:08 +01:00
LICENSE= AL2
Update to 0.6.1 bugfix release. Add LICENSE. Unfortunately remove javadocs.
2011-01-10 15:28:55 +01:00
LICENSE_FILE= ${WRKSRC}/LICENSE
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
USE_JAVA= yes
Decommissioning java 1.5 (EOLed since October 2009): suppress any reference to JAVA_VERSION= 1.5+ (part2)
2012-12-10 14:18:28 +01:00
JAVA_VERSION= 1.6+
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
NO_BUILD= yes
WRKSRC= ${WRKDIR}/apache-${PORTNAME}-${PORTVERSION}
Update to 0.7 release.
2011-08-09 13:59:59 +02:00
PLIST_FILES= %%JAVAJARDIR%%/apache-${PORTNAME}-core.jar \
%%JAVAJARDIR%%/apache-${PORTNAME}-dom.jar \
%%JAVAJARDIR%%/apache-${PORTNAME}-storage.jar
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
PORTDOCS= *
Add NO_STAGE all over the place in preparation for the staging support (cat: mail)
2013-09-20 21:59:12 +02:00
NO_STAGE= yes
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
do-install:
Update to 0.7 release.
2011-08-09 13:59:59 +02:00
${INSTALL_DATA} ${WRKSRC}/apache-${PORTNAME}-core-${PORTVERSION}.jar \
${JAVAJARDIR}/apache-${PORTNAME}-core.jar
${INSTALL_DATA} ${WRKSRC}/apache-${PORTNAME}-dom-${PORTVERSION}.jar \
${JAVAJARDIR}/apache-${PORTNAME}-dom.jar
${INSTALL_DATA} ${WRKSRC}/apache-${PORTNAME}-storage-${PORTVERSION}.jar \
${JAVAJARDIR}/apache-${PORTNAME}-storage.jar
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
.if !defined(NOPORTDOCS)
Update to 0.7 release.
2011-08-09 13:59:59 +02:00
${MKDIR} ${DOCSDIR}
${INSTALL_DATA} ${WRKSRC}/RELEASE_NOTES.txt ${DOCSDIR}
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain rfc822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream. It won't do any decoding of base64 or quoted-printable encoded header fields and bodies. The parser has been designed to be extremely tolerant against messages violating the standards. mime4j can also be used to build a tree representation of an e-mail message using the Message class. Using this facility mime4j automatically handles the decoding of fields and bodies and uses temporary files for large attachments. WWW: http://james.apache.org/mime4j/
2008-09-03 10:04:41 +02:00
.endif
.include <bsd.port.mk>
Reference in a new issue Copy permalink