A pile of shonky packages (with errors)

[Matthew Vernon <matthew@debian.org>]

Hi,

I've been doing a bit more work on this, and have different problems
now. I've put a whole pile of source and binary packages, and build logs
here:

http://www.chiark.greenend.org.uk/~matthewv/javadebs/

The thing I'm trying to get right is libxmltooling-java [0]. The
problems I'm having with that are:

i) lintian complains that my classpaths are wrong:

W: libxmltooling-java: missing-classpath libbcprov-java,
libcommons-codec-java, libjaxp1.3-java, libjoda-time-java,
libnot-yet-commons-ssl-java, libshib-parent-project2-java,
libxalan2-java, libxerces2-java, libxml-commons-resolver1.1-java,
libxml-security-java

ii) despite my having told "mh_make" that I wanted to install as version
1.x, it's installing only as version 1.4.2-SNAPSHOT only

iii) the .pom file ends up with garbage in which maven later chokes on:
Failed to parse
/home/mcv21/packages/libxmltooling-java-1.4.2/debian/maven-repo/org/opensaml/xmltooling/1.4.2-SNAPSHOT/xmltooling-1.4.2-SNAPSHOT.pom
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[19,13]
Message: start tag unexpected character $

this is because of:
<debian.${xerces.groupId}.serializer.originalVersion>debian</debian.${xerces.groupId}.serializer.originalVersion>

This is a mis-parse of a rule in maven.rules, I think, and it would be
better to suppress it entirely. How?

By way of background, the other packages are:

* libjcip-annotations-java-doc_20060626-3.1 - possible NMU to add maven
support to this package

* libnot-yet-commons-ssl-java_0.3.9-3 - package of a dependency of
libxmltooling-java

* libshib-parent-project2-java_1-1 - the parent POM of
libxmltooling-java (and some other things that the IdP depends upon);
packaging this up seemed the best way to get it into my project? The
compile errors I had yesterday were related to it missing dependencies
that are specified in this POM

I'm hoping that if I can get libxmltooling-java into sensible shape,
then packaging up the other dependencies and the IdP itself will be
easier...! The upstream site is:

https://wiki.shibboleth.net/confluence/display/SHIB2/SourceAccess

Thanks,

Matthew

[0] Actually, that's not quite true - I really want to end up with a
shibboleth IdP package, and libxmltooling-java's the first big
dependency of that, produced by the same upstreatm