Sync maven 3.0.4-1 (universe) from Debian unstable (main)

[Blair Zajac]

Please sync maven 3.0.4-1 (universe) from Debian unstable (main)

All changelog entries:

maven (3.0.4-1) unstable; urgency=low

  * New upstream final release (same as RC5).
  * Upload to unstable this time.
  * Remove Michael, Ludovic and Torsten from Uploaders: I've added them by cut
    and pasting from maven2 package, without their approval
    (feel free to re-add yourself if you want).
  * Refresh d/patches/dep_versions.diff.

 -- Damien Raude-Morvan <email address hidden> Sat, 21 Jan 2012 13:45:19 +0100

maven (3.0.4~rc3-1) experimental; urgency=low

  * New upstream major release (Closes: #592218).

 -- Damien Raude-Morvan <email address hidden> Mon, 19 Dec 2011 20:17:37 +0100

[Blair Zajac (blair)]

Currently precise only has maven2 while maven 3.0.x is the current major release. It aims to be compatible with Maven 2 [1].

[1] http://maven.apache.org/docs/3.0.4/release-notes.html

However, there appear to be a number of dependencies that need to be synced over. If there's a chance that this could make it into 12.04, I could get a list of dependency packages that would also need to be synced.

[Martin Pitt (pitti)]

Syncing maven seems fine to me. Can you please give the list of all packages that we need to sync for this? Thanks!

[Blair Zajac (blair)]

I'll start on the list.

Do you want them all listed in this ticket or separate tickets for each one?

[Blair Zajac (blair)]

Actually, it wasn't bad, the only additional package I needed to install directly from Debian was libaether-java from the aether package.

Here's what works:

$ apt-get install maven2
$ apt-get purge maven2
$ apt-get install libasync-http-client-java \
  libguava-java \
  libplexus-classworlds2-java \
  libplexus-containers1.5-java \
  libplexus-utils2-java \
  libsisu-guice-java \
  libsisu-ioc-java
$ wget http://ftp.debian.org/debian/pool/main/a/aether/libaether-java_1.13.1-2_all.deb
$ dpkg -i libaether-java_1.13.1-2_all.deb
$ wget http://ftp.debian.org/debian/pool/main/m/maven/maven_3.0.4-1_all.deb
$ dpkg -i maven_3.0.4-1_all.deb

Doing this works with no complaints from dpkg, i.e. I didn't need to run 'apt-get -f install'.

Another issue is if Ubuntu's dependencies are up to date to provide what Maven 3 needs, it's not easily to tell if something in Maven will break. Should we take a precise system with no maven dependencies installed, install maven and see what is installed, then sync those all from Debian?

[Bryce Harrington (bryce)]

> Should we take a precise system with no maven dependencies installed, install maven and see what is installed, then sync those all from Debian?

Sure, that seems like a logical next step.

Re-subscribe sponsors when you have the list tested and ready.

[Blair Zajac (blair)]

Since I opened this libaether-java is now in Ubuntu, the same version as Debian, so that issue is resolved.

Here's what I did to see about dependencies, I took a fresh VM install, apt-get install libaether-java and then dpkg -i maven from Debian. Then used a hacked version of requestsync to compare Ubuntu's and Debian's package versions.

--- Upstream source is newer in Debian

ca-certificates-java - 20111223 compared to 20110912ubuntu4
java-common - 0.46 compared to 0.43ubuntu2
libhttpcore-java - 4.1.4-1 compared to 4.1-1

My guess is that libhttpcore-java is the only really important one.

--- Upstream source is the same but Debian packaging is newer

antlr - 2.7.7+dfsg-4 compared to 2.7.7+dfsg-3
aspectj - 1.6.12+dfsg-3 compared to 1.6.12+dfsg-2
fop - 1:1.0.dfsg2-6 compared to 1:1.0.dfsg2-4
libaopalliance-java - 20070526-5 compared to 20070526-4
libbsf-java - 1:2.4.0-5 compared to 1:2.4.0-4ubuntu1
libcommons-jexl-java - 1.1-3 compared to 1.1-2
libcommons-logging-java - 1.1.1-9 compared to 1.1.1-8
libcommons-validator-java - 1:1.3.1-8 compared to 1:1.3.1-7
jaxme - 0.5.2+dfsg-6 compared to 0.5.2+dfsg-5
apache-log4j1.2 - 1.2.16-3 compared to 1.2.16-2ubuntu2
libsaxon-java - 1:6.5.5-8 compared to 1:6.5.5-7ubuntu1
sisu-ioc - 2.3.0-2 compared to 2.3.0-1
werken.xpath - 0.9.4-14 compared to 0.9.4-13
xmlgraphics-commons - 1.4.dfsg-4 compared to 1.4.dfsg-3ubuntu1
libexcalibur-logkit-java - 2.0-9 compared to 2.0-8ubuntu1
wagon - 1.0.0-2 compared to 1.0.0-1ubuntu1

--- Completely different versions:

batik - 1.7-8 compared to 1.7.ubuntu-6ubuntu1

--- C packages that probably don't matter:

libxcb1-dev - 1.8-1 compared to 1.7-4

[Blair Zajac (blair)]

For reference, the script I used to generate the differences.

[Blair Zajac (blair)]

For testing, I built Maven from its own source code in the fresh VM using the Debian package and it worked fine.

[Colin Watson (cjwatson)]

httpcomponents-core (binary package libhttpcore-java): synced
antlr: no change needed, Debian change was for mono transition
aspectj: synced
fop: synced
libaopalliance-java: synced
libbsf-java: determined that Ubuntu changes are no longer necessary; synced
libcommons-jexl-java: synced
libcommons-logging-java: synced, but will require MIR of libcommons-parent-java
libcommons-validator-java: synced
jaxme: synced
apache-log4j1.2: unmerged Ubuntu changes; needs to be merged not synced
libsaxon-java: determined that Ubuntu changes are no longer necessary; synced
sisu-ioc: synced
werken.xpath: synced
xmlgraphics-commons: unmerged Ubuntu changes; needs to be merged not synced
excalibur-logkit (binary package libexcalibur-logkit-java): determined that Ubuntu changes are no longer necessary; synced
wagon: determined that Ubuntu changes are no longer necessary; synced
batik: requires fiddly manual fakesync, but doesn't seem necessary here

Could you progress the ones that require merges, and check how precise looks after all of this has built and published?

[Blair Zajac (blair)]

For apache-log4j1.2 https://bugs.launchpad.net/ubuntu/+source/apache-log4j1.2/+bug/922890 .
For xmlgraphics-commons https://bugs.launchpad.net/ubuntu/+bug/922893 .

[James Page (james-page)]

Hi Blair

Thanks for raising the two bug reports for packages that require merges; As the last uploader for these packages I'll pick those up.

Looking at the changelogs I don't think that they are required to support the sync of maven; apologies but I already requested the sync before noticing this ticket (my bad) so hopefully it will be accepted from the NEW queue in the next few days.

[Blair Zajac (blair)]

Hi James,

That was my sense too that a merge wasn't required to satisfy maven itself, but given I'm new to Ubuntu packaging I took on the request.

BTW, since I have your attention, what is your take on the one MIR request in the maven sync request: "libcommons-logging-java: synced, but will require MIR of libcommons-parent-java"?

Regards,
Blair

On Jan 28, 2012, at 12:38 AM, James Page <email address hidden> wrote:

> Hi Blair
>
> Thanks for raising the two bug reports for packages that require merges;
> As the last uploader for these packages I'll pick those up.
>
> Looking at the changelogs I don't think that they are required to
> support the sync of maven; apologies but I already requested the sync
> before noticing this ticket (my bad) so hopefully it will be accepted
> from the NEW queue in the next few days.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/920284
>
> Title:
> Sync maven 3.0.4-1 (universe) from Debian unstable (main)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/920284/+subscriptions
>

[Micah Gersten (micahg)]

This was sync'd as 3.0.4-2 into precise

[Blair Zajac (blair)]

Thanks for the quick sync, appreciate it.

Regards,
Blair