[
https://issues.apache.org/jira/browse/NIFI-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Youtsey closed NIFI-4455.
--------------------------------
> nifi-nar-maven-plugin - Nar-Dependency-Id not being written to manifest
> -----------------------------------------------------------------------
>
> Key: NIFI-4455
> URL: https://issues.apache.org/jira/browse/NIFI-4455
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 1.1.0
> Reporter: Steven Youtsey
> Priority: Minor
> Labels: maven
> Fix For: 1.2.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
