Just following up on what Joe said, take a look at this section on the wiki:
https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Extensions#MavenProjectsforExtensions-Inheritance Thanks, Bryan On Fri, Mar 31, 2017 at 9:08 AM, Joe Witt <[email protected]> wrote: > Michal > > The archetype and existing components all extend from a common parent > in nifi. If you want to build extensions that are not part of the > apache nifi maven build/structure/hierarchy you can have your own > parent and details. This is a perfectly fine thing to do. The sort > of customization you're showing begins that process of having your own > path differ from the norm or you can do it more fully by defining your > own parent pom and using that instead of the nifi one. > > Thanks > > On Fri, Mar 31, 2017 at 4:44 AM, Michal Klempa <[email protected]> > wrote: >> Hi there, >> I am working on my own processor bundle, however, I came into trouble >> with deployment of my bundle as maven artifact into Artifactory. >> >> My bundle was create using the maven archetype and there are three projects: >> 1. main pom.xml: >> <parent> >> <groupId>org.apache.nifi</groupId> >> <artifactId>nifi-nar-bundles</artifactId> >> <version>1.1.1</version> >> </parent> >> >> <groupId>eu.ideata.stream.nifi</groupId> >> <artifactId>nifi-stream-bundle</artifactId> >> <version>1.0.2-SNAPSHOT</version> >> <packaging>pom</packaging> >> >> <modules> >> <module>nifi-stream-processors</module> >> <module>nifi-stream-nar</module> >> </modules> >> ... >> >> 2. two modules, not important for now. >> >> >> What is the problem, that when I deploy using mvn deploy, I get error from >> nexus-staging-maven-plugin >> >> that it cannot reach the https://repository.apache.org/ repository. Of >> course, I am not authorized to >> deploy there and I am unwilling to deploy there. I have my private >> Artifactory instance however. >> >> I was tracing the parents structure of pom files, and found that >> <groupId>org.apache.nifi</groupId> >> <artifactId>nifi-nar-bundles</artifactId> >> is child of >> <groupId>org.apache.nifi</groupId> >> <artifactId>nifi</artifactId> >> <version>1.1.1</version> >> which has the nexus-staging-maven-plugin included in the build: >> https://github.com/apache/nifi/blob/master/pom.xml#L1710 >> >> This is causing my issues and I was able to circumvent the execution >> of nexus-staging-maven-plugin by adding >> <build> >> <plugins> >> <plugin> >> <groupId>org.sonatype.plugins</groupId> >> <artifactId>nexus-staging-maven-plugin</artifactId> >> <version>1.6.5</version> >> <extensions>false</extensions> >> <configuration> >> >> <stagingProgressTimeoutMinutes>15</stagingProgressTimeoutMinutes> >> <serverId>repository.apache.org</serverId> >> <nexusUrl>https://repository.apache.org/</nexusUrl> >> </configuration> >> </plugin> >> </plugins> >> </build> >> >> into my main pom.xml, see the <extensions>false</extensions> which, >> turns off this plugin. >> >> Have anybody else observed this issue? How did you dealt with it ? Or >> maybe I am doing something wrong, correct me please. >> >> Regards, Michal Klempa
