gradle: Avoid setting a manifest object by bjhargrave · Pull Request #5276 · bndtools/bnd (original) (raw)

Skip to content

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@bjhargrave

Instead of setting a manifest object in the task so that we can
set the effective manifest, after building we merge the generated
manifest into the existing manifest object.

Fixes #5275

This was referenced

Jun 3, 2022

@bjhargrave bjhargrave changed the titlegradle: Use a proxy to wrap the existing manifest gradle: Avoid setting a manifest object

Jun 4, 2022

@bjhargrave

Rather than setting a manifest object in the task so that we can set the effective manifest after building, we instead merge the generated manifest into the existing manifest object.

Fixes bndtools#5275

Signed-off-by: BJ Hargrave bj@hargrave.dev

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

Labels

maint-candidate

Issues or pull requests that are candidates for a maintenance release

1 participant

@bjhargrave