- Update to 1.2 Herve, I haven't yet tested the packages that depend on commons-cli. Is the best test just to start them up? I assume that use commons-cli for command line option parsing. Please let me know if there is a better test I can do. Also, I changed to using the pre-compiled JAR since 1.2 required Maven to build and I wasn't sure how much infrastructure we have in place to do that yet. We can do the compile from source instead if that is feasible (although I'm beginning to wonder about the point of it, since the source is included in the binary distribution if you want to examine it). Port maintainer (hq@FreeBSD.org) is cc'd. Generated with FreeBSD Port Tools 0.99
Responsible Changed From-To: freebsd-ports-bugs->hq Over to maintainer (via the GNATS Auto Assign Tool)
hq 2010-12-12 15:07:56 UTC FreeBSD ports repository Modified files: java/jakarta-commons-cli Makefile distinfo Log: - Update to 1.2 - Use binary distribution PR: 152767 Submitted by: glewis Revision Changes Path 1.15 +14 -23 ports/java/jakarta-commons-cli/Makefile 1.4 +2 -3 ports/java/jakarta-commons-cli/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed Greg, There were no ports dependending on commons-cli (at least that's what portsearch(1) reported) so I just commited your patch. Regarding binary vs source: I haven't find a way yet to build ports using Maven. And as you said, the source code is available in the binary distribution so I guess it is fine with a binary port. Thanks for your patch. Herve PS: sorry for the delay