bndmanifest and java-library intermodule dependencies

Open

#114 opened on Jan 13, 2020 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: java
Domain: build-system

Research direction

Start with the failing Travis build at the referenced :durian-swt:jar task and compare the reported failure with the workaround commit in diffplug/durian-swt. Trace how the java-library api dependency and bndmanifest handle the intermodule jar, then verify that the missing-jar failure no longer occurs in a comparable multi-module build.

Written by the indexing model from the issue text.

Description

bug

In https://github.com/diffplug/durian-swt/pull/7/commits/496386ecebd023075b03a041d238af8d02a29469 I used java-library in a multi-module project, and I declared an api dependency on another module within the project. I then saw intermittent errors like this:

> Task :durian-swt:jar FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':durian-swt:jar'.
> A Jar can only accept a file or directory that exists: /home/travis/build/diffplug/durian-swt/durian-swt.os/build/libs/durian-swt.os-3.3.0.jar

The workaround is https://github.com/diffplug/durian-swt/pull/7/commits/b3df3311d6ef3d6ce22756512a7e742227091e3c

Dominant language: Java
Stars: 137
Forks: 33
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.