I would like to build some of the Apache Commons packages that I maintain with maven2 instead of ant, because in upstream's own words, the ant build is secondary and will not be updated to include generation of OSGI manifests, for example, because of infrastructure restrictions. The maven2 build does generate the OSGI manifests, so instantly there'll be a few patches we could drop simply by switching to a supported build system.
However, to do this I think we need the commons-parent.pom in maven2-common-poms.
The Apache Commons projects tend now to ship their own project specific pom with the source, and include the commons-parent pom that contains the bits that are common across all the commons projects (like the OSGI manifest bit).
Is it possible to get the commons-codec.pom and commons-digester.pom files removed from this package and replaced with commons-parent.pom instead?
The commons-codec 1.4 build gets past the first hurdle if that file exists at /usr/share/maven2/default_poms/org.apache.commons-commons-parent.pom
I'm making this bug depend on maven update instead of blocking it. We can always do this when maven is updated and it's better to update maven entirely before taking care for the dependent packages.
commons-parent is added to maven2-common-poms in rawhide.