[
https://issues.apache.org/jira/browse/NIFI-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-11879.
-----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> Maven install&deploy command not work while specifing classifier for
> generated jars.
> ------------------------------------------------------------------------------------
>
> Key: NIFI-11879
> URL: https://issues.apache.org/jira/browse/NIFI-11879
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.21.0
> Reporter: Clow
> Assignee: Nathan Gough
> Priority: Minor
> Attachments: image-2023-07-31-11-52-04-874.png
>
>
> For some reason, we should specify classifer for maven-source-plugin and
> maven-jar-plugin, it works fine for maven package instuction. But when we
> want to install those jars into local repository and remote nexus. it gets
> below,
> !image-2023-07-31-11-52-04-874.png|width=973,height=519!
> h2. Reproduce behaviour
> add plugins into pom.xml and specify classifiers. pasted code snippet below.
> {code:java}
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-source-plugin</artifactId>
> <configuration>
> <classifier>provided-sources</classifier>
> </configuration>
> <executions>
> <execution>
> <id>attach-sources</id>
> <goals>
> <goal>jar</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <configuration>
> <classifier>provided</classifier>
> </configuration>
> </plugin>
> </plugins>
> </build> {code}
> and then execute maven command below,
> {code:java}
> mvn clean install // or mvn clean deploy{code}
> h2. Workaround
> downgrade maven install plugin from 3.1.0 to 2.5.2, it works fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
