Skip to content

fix(tooling): support non-standard feature classifier names in karaf-maven-plugin (#2144)#2310

Open
jbonofre wants to merge 1 commit intoapache:mainfrom
jbonofre:gh-2144
Open

fix(tooling): support non-standard feature classifier names in karaf-maven-plugin (#2144)#2310
jbonofre wants to merge 1 commit intoapache:mainfrom
jbonofre:gh-2144

Conversation

@jbonofre
Copy link
Copy Markdown
Member

The feature descriptor generator hardcoded the "features" classifier, causing dependencies with non-standard classifiers (e.g. "features-core") to be inlined as bundles instead of recognized as feature dependencies.

  • Dependency31Helper.isFeature(): match classifiers starting with "features"
  • GenerateDescriptorMojo.processFeatureArtifact(): remove redundant classifier check
  • GenerateDescriptorMojo: use configured attachmentArtifactClassifier instead of hardcoded FEATURE_CLASSIFIER when setting the project artifact
  • AssemblyMojo.getType() and RunMojo.getAttachedFeatureFile(): same classifier fix

…maven-plugin (apache#2144)

The feature descriptor generator hardcoded the "features" classifier,
causing dependencies with non-standard classifiers (e.g. "features-core")
to be inlined as bundles instead of recognized as feature dependencies.

- Dependency31Helper.isFeature(): match classifiers starting with "features"
- GenerateDescriptorMojo.processFeatureArtifact(): remove redundant classifier check
- GenerateDescriptorMojo: use configured attachmentArtifactClassifier instead of
  hardcoded FEATURE_CLASSIFIER when setting the project artifact
- AssemblyMojo.getType() and RunMojo.getAttachedFeatureFile(): same classifier fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

karaf-maven-plugin feature generator doesn't support none standard feature classifier names

1 participant