Bug#551126: libcommons-httpclient-java: Maven POMs: commons-httpclient is not anymore

[Damien Raude-Morvan]

X-Debbugs-Cc: Michael Koch <konqueror at gmx.de>
Package: libcommons-httpclient-java
Version: 3.1-6
Severity: normal

Hi,

With upload of commons-httpclient 3.1-6, there was a revert on Maven POM 
version mapping :

  --
  commons-httpclient (3.1-6) unstable; urgency=low

    * Don't map version of commons-httpclient explicitly.
    * Added myself to Uploaders.
    * Updated Standards-Version to 3.8.3.

   -- Michael Koch <konqueror at gmx.de>  Mon, 05 Oct 2009 12:23:44 +0200
  --

This update in version mapping change Maven POM's installation from previous :

/usr/share/maven-repo/commons-httpclient/commons-httpclient/3.1/commons-
httpclient-3.1.pom
/usr/share/maven-repo/commons-httpclient/commons-httpclient/3.x/commons-
httpclient-3.x.pom

to new location :

/usr/share/maven-repo/commons-httpclient/commons-httpclient/3.1/commons-
httpclient-3.1.pom
/usr/share/maven-repo/commons-httpclient/commons-httpclient/debian/commons-
httpclient-debian.pom


This have the side effect of FTBFS 25+ packages :

logs/failed-clirr-maven-plugin-2.2.2-2
logs/failed-doxia-maven-plugin-1.1.1-1
logs/failed-maven-antrun-plugin-1.3-1
logs/failed-maven-clean-plugin-2.3-3
logs/failed-maven-compiler-plugin-2.0.2-4
logs/failed-maven-debian-helper-0.6
logs/failed-maven-dependency-plugin-2.1-2
logs/failed-maven-docck-plugin-1.0-2
logs/failed-maven-ear-plugin-2.3.2-1
logs/failed-maven-ejb-plugin-2.2-1
logs/failed-maven-install-plugin-2.3-2
logs/failed-maven-invoker-plugin-1.3-2
logs/failed-maven-jar-plugin-2.2-4
logs/failed-maven-javadoc-plugin-2.5-2
logs/failed-maven-plugin-tools-2.5-2
logs/failed-maven-repository-builder-1.0~alpha2-1
logs/failed-maven-resources-plugin-2.3-5
logs/failed-maven-shade-plugin-1.2.1-2
logs/failed-maven-site-plugin-2.0-2
logs/failed-maven-war-plugin-2.1~beta1-1
logs/failed-modello-maven-plugin-1.1-1
logs/failed-plexus-active-collections-1.0~beta2-1
logs/failed-plexus-component-metadata-1.0~beta3.0.7-2
logs/failed-plexus-maven-plugin-1.3.8-4
logs/failed-surefire-2.4.3-3


Each time error is :
"
Missing:
----------
1) commons-httpclient:commons-httpclient:jar:3.x

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=commons-httpclient -
DartifactId=commons-httpclient -Dversion=3.x -Dpackaging=jar -
Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file 
there:
      mvn deploy:deploy-file -DgroupId=commons-httpclient -
DartifactId=commons-httpclient -Dversion=3.x -Dpackaging=jar -
Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.apache.maven.plugins:maven-plugin-plugin:maven-plugin:2.5
        2) org.apache.maven.doxia:doxia-site-renderer:jar:debian
        3) org.apache.maven.doxia:doxia-core:jar:debian
        4) commons-httpclient:commons-httpclient:jar:3.x
"

We have 2 possible fix :
- revert change to commons-httpclient version mapping -> install with 3.x 
instead of standard "debian"
- fix maven-doxia-plugin to use "debian" version mapping

But, first, I would like to understand the reasoning behind this change in 
version mapping. Michael could you please describe your process ?

Cheers,
-- 
Damien Raude-Morvan - http://damien.raude-morvan.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20091015/b7544224/attachment.pgp>