Skip to content
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.

Improve behaviour of vendor filtering for pure Maven-built JARs #131

Open
pfistererm opened this issue Sep 16, 2020 · 0 comments
Open

Improve behaviour of vendor filtering for pure Maven-built JARs #131

pfistererm opened this issue Sep 16, 2020 · 0 comments
Labels
Prio: Triage Triage Priority Status: Pending Issue or PR awaits response Type: Feature Issue or PR is a new feature

Comments

@pfistererm
Copy link
Contributor

Currently, vendor filtering is based on the value 'Bundle-Vendor' in the MANIFEST.MF file, which is appropiate for JARs that are OSGi bundles. For JARs that are build with a standard Maven build, this is incenvenient, since the MANIFEST often is generated automatically. For these cases, it would be more convenient to do vendor filtering based on a value in the POM (suggestion: organisation / name).

Feature request

Expected Behavior - What where you expecting to happen?

Current Behavior - What happens?

Possible Solution

Context

Notes and further information

@pfistererm pfistererm added Type: Feature Issue or PR is a new feature Status: Pending Issue or PR awaits response Prio: Triage Triage Priority labels Sep 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Prio: Triage Triage Priority Status: Pending Issue or PR awaits response Type: Feature Issue or PR is a new feature
Development

No branches or pull requests

1 participant