Dear Maintainer,

The wagon source package will not build in a fully offline build environment;
by default the package target is called during the build and as a result the
javadoc target (called separately) cannot see the just built artifacts.

In Ubuntu, the attached patch was applied to achieve the following:

  * Fix FTBFS in offline build environments:
    - d/rules: Switch to using 'install' target instead of default 'package'
      target for build to ensure that artifacts built by this package can
      be accessed locally during javadoc generation.
    - d/control: Added libmaven-install-plugin-java to BDI's.
  * d/libwagon-java.poms: Added --java-lib to ensure that jar files are also
    installed into /usr/share/java.

Thanks for considering the patch.

- -- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
iQIcBAEBCAAGBQJPlqELAAoJEL/srsug59jDIyIP/R01f+tUdR7aYmOUJy9tpF0s
AoK/LkD8mx4cEuJTfYN2yIKjSIubJ2z1nRx16Lpsq6PVxIrVNZu8dvzjCXhRUsLz
2i1cI9HWWGp1jHK30WPWRQKbG+txZg7Kn5RtMTnHnxFfDJly9uo4y4g/QmdPuJvE
aLDB5xtI0CiWTKZ5wNoPacc8a5jTcgEu5ehUVhlIgvIJ7vcsOinPMONS3xLK1L4K
o+L+Gnp4QJ83NoFJyqEdaUccwSrxLtOl+O8YVHOptdYa4U9IbsPzNMOrZYRopPAP
+V7XuCtN7YutaibeDXbsJGibWKk6uGuYwoF4/G74gIZAGvwqeH5FaSEqe9SuS+6v
uhmDzK4ckUg8/lhO066PGirtP4noiVvqE5YeN620hiRR7k+NxUgHZjq2+bz1fR6G
vQpjKAZAxwl3shSifTYqSD9N+OU9t+AUxesmzKIYADk+SR+Q3Ddq5v3gi8ZUY8Eo
KYQhuPd0Zx18mOJf+skinDT4ekh0ZsppBVN0vbq8pWTpauU74JgT9MdKlL3qfUpC
UlDKuULplOAEgFjLH+JEMZ+vmvky96KOM/GDlPIXjR5ghAp1ae4I5HdhDSGz1/yG
nRHsP6xEvNsBLQab0JKiGvHKtnVG1haoymAcMoy7ifu/Og4KZBaxM/ZE3fmHrkUh
WxBX0g/fBa7hLGzasfHn
=qFEY
-----END PGP SIGNATURE-----

Hello James,

thank you for submitting this patch.  Currently the package FTBFS for me
in a clean sid chroot after applying the patch with the following message:

Is the behavior of m-d-h perhaps different in Ubuntu?

Thank you,
tony

I think the behaviour is the same; I've seen this in other packages
where the first upload of a new upstream release using m-d-h with
'install' rather than 'package' works fine - however subsequent builds
fail because of a circular dependency which pulls the same package
into the build-deps.

My bad - I though I had checked for that specific problem but looking
at my build log I did not check enough!

We fixed this in libhibernate3-java by using the install target for a
new upstream release and the package target for subsequent updates to
the same upstream version.

I'll endeavour to update the patch in the next couple of days.

Cheers

James

Hello,

I am hitting this issue if building ubuntu package versioned as 1.0.0-2ubuntu2.

Debian package versioned 1.0.0-2 builds fine for me.

Note if Debian package really FTBFS, then consider setting severity to serious.

If you have a patch ready I would be willing to test/build it.

Regards,