[NIFI-4455] nifi-nar-maven-plugin - Nar-Dependency-Id not being written to manifest

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.2.0
• Component/s: Tools and Build
• Labels: maven
• Assignee: Unassigned
• Reporter: Steven Youtsey
• Created: 03/Oct/17 14:25
• Updated: 06/Nov/17 16:55
• Resolved: 06/Nov/17 16:54

Description

Within a nar pom that extends/depends on a parent nar, the parent nar's id is not written to the Nar-Dependency-Id in the Manifest file when the parent nar's maven artifact contains a maven classifier.

<dependency>
<groupId>myGroup</groupId>
<artifactId>my-service-api-nar</artifactId>
<version>1.2.3</version>
<type>nar</type>
<classifier>gpu</classifier>
</dependency>

produces...

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Built-By: unattributed
Nar-Id: my-service
Created-By: Apache Maven 3.3.3
Build-Jdk: 1.8.0_131

The workaround for this was to override the plugin and add the Nar-Dependency-Id via manifestEntries.