Control: block 869018 with 869361

Am 22.07.2017 um 19:04 schrieb tony mancill:
> Source: maven-bundle-plugin
> Severity: serious
> Justification: 4
> It looks like the update to maven-archiver [1] (for whatever reason,
> doesn't have a news entry for the upload yet) break
> maven-bundle-plugin, which is the root cause of FTBFS #869279 [2] and
> probably many others.
>> [ERROR]
>> /build/maven-bundle-plugin-2.5.4/src/main/java/org/apache/felix/bundleplugin/[760,89]
>> incompatible types: org.apache.maven.archiver.MavenArchiveConfiguration
>> cannot be converted to org.apache.maven.archiver.ManifestConfiguration
> Shall we go ahead and update maven-bundle-plugin to 3.3.0, or are there
> advantages to patching the 2.5.x package to work with the newer
> maven-archiver?

Easymock is also affected by this bug. [1] When I fix the
incompatibility with the new version of maven-jar-plugin I get the
following error message:

[ERROR] Failed to execute goal
org.apache.felix:maven-bundle-plugin:2.5.4:manifest (bundle-manifest) on
project easymock: Execution bundle-manifest of goal
org.apache.felix:maven-bundle-plugin:2.5.4:manifest failed: An API
incompatibility was encountered while executing

I think we should upgrade maven-bundle-plugin too which would be
consistent. I also would like to suggest that we try to update core
build tools like Maven and related plugins step by step which means
update package1, wait for FTBFS bugs being reported, fix fallout, then
update package2 and repeat. Sometimes I lose track of which update broke
which package and it takes too much time to figure out the root cause.
I'm willing to help but I need more pointers what should be done in
which order.



Attachment: signature.asc
Description: OpenPGP digital signature

This is the maintainer address of Debian's Java team
Please use for discussions and questions.

Reply via email to