Thank you for the upload Tony. This is probably a maven-ant-helper bug, because the pom.xml for modello specifies UTF-8 as the source encoding and the parameter isn't passed to the javadoc generator. Assuming we no longer care about bootstrapping Maven properly (that is, all its transitive dependencies should be built with something that doesn't depend on Maven. I'm pretty sure that is already no longer true) we could gradually replace maven-ant-helper with maven-debian-helper as the build helper for these packages. The packages affected are: bnd classworlds clirr commons-jci eclipse findbugs-bcel jackrabbit libcommons-cli-java libcommons-net2-java libjboss-marshalling-java libonemind-commons-invoke-java libspin-java libswingx1-java libxbean-java libxstream-java maven-dependency-analyzer maven-filtering maven-invoker maven-plugin-tools modello modello1.4 plexus-ant-factory plexus-archiver plexus-bsh-factory plexus-cdc plexus-classworlds2 plexus-component-metadata plexus-container-default plexus-containers plexus-containers1.5 plexus-io plexus-utils2 qdox surefire tiles xmlunit Emmanuel Bourg Le 14/01/2014 07:58, tony mancill a écrit : > > Hi Emmanuel, list-at-large: > > I noticed that the -doc binary packages for these two packages (and > probably many others) result in empty packages unless the locales > package is installed and at least LC_ALL set to $something.UTF-8 at the > beginning of the build. Without this, the javadoc build complains with > this error: > > error: unmappable character for encoding ASCII > > but doesn't fail the build. Therefore, folks (re)building packages > should take care to verify with debc or similar that the resulting > binary package contains the expected files. > > Not having a locale set is perhaps a bit particular to using a clean > base chroot for package building, so not everyone will run into this. > > However, having just been through a similar experience (read: "hassle") > with migrating from ruby 1.8 -> 1.9.1 (for the build system in jblas), > it got me to thinking that since some build systems expect to be run > within a given locale, perhaps we could help this with some tools and/or > policy. Tools, because I'd hate to have to every debian/rules have to > explicitly install locales, generate an appropriate locale, then export > it to the build environment. And perhaps policy too, because it seems > like we shouldn't expect people to have to constantly rejigger their > locale to build any given package. (Again, maybe the tool handles that.) > > Anyway, not an urgent issue, but I think there may be other Java > packages affected. > > tony >
Attachment:
signature.asc
Description: OpenPGP digital signature