On Sun, 3 Apr 2011 16:54:28 +0200 Miklos Vajna <vmik...@frugalware.org> wrote:
> Rene also suggested that the dependency can be declared in junit's > manifest file, which is the place where this is fixed e.g. in Debian, > so my configure change turned out to be unnecessary. On current debians (I just tried sid) and Ubuntus there is the no classpath set in the system junit jar that also does not contain hamcrest. Since this problem is widespread: How about checking, if either: - the jar sets an classpath in the manifest - the jar contains hamcrest and complain explicitly "your junit jar neither sets a classpath nor includes hamcrest -- please provide a full junit jar or use --without-junit" if neither is the case. This also helps people making the right choice with the upstream jars, where both (including hamcrest and excluding hamcrest) are available. Doing this little additional testing might prevent some newcomers to run away screaming (it might not be the first issue they hit on their first build). Best, Bjoern -- https://launchpad.net/~bjoern-michaelsen
signature.asc
Description: PGP signature
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
