Re: NiFi custom extension and deploy phase on Maven
Exactly. The configuration on my pom. org.apache.nifi nifi-nar-bundles 1.23.2 Offering one without all ASF-isms, it can be nice also.. Thanks Le sam. 9 déc. 2023 à 19:03, Joe Witt a écrit : > Etienne, > > Are you using our nifi poms as your parent pom of your extensions? I do > wonder if perhaps we should offer one that doesn't tie to all our ASF-isms > > Thanks > > On Sat, Dec 9, 2023 at 10:54 AM Etienne Jouvin > wrote: > >> Hello all; >> >> Since now, I never push my extensions to any Nexus or Artifactory. >> But now I must do it. >> >> The deploy Maven deploy is in failure and I notice it comes from the >> configuration for the plugin nexus-staging-maven-plugin. >> >> The configuration comes from the artifact nifi, where we can find the >> following configuration. >> >> >> >> org.sonatype.plugins >> >> nexus-staging-maven-plugin >> >> 1.6.13 >> >> true >> >> >> >> 15 >> >> repository.apache.org >> >> https://repository.apache.org/ >> >> >> >> >> >> >> Two things : >> I did not have any issue when I wanted to push my extension in SNAPSHOT >> version, except I had to configure the enforcer to not fire exception >> >> And to be able to push my extensions in my custom Artifactory, I had to >> disable it by the following configuration, in the build node at my root >> pom.xml file : >> >> >> >> >> >> org.sonatype.plugins >> >> nexus-staging-maven-plugin >> >> >> >> true >> >> >> >> >> >> >> What do you think if you put your build configuration inside a profile ? >> Like this, we will not have to add a custom configuration. >> >> Regards >> >> Etienne Jouvin >> >>
Re: NiFi custom extension and deploy phase on Maven
Etienne, Are you using our nifi poms as your parent pom of your extensions? I do wonder if perhaps we should offer one that doesn't tie to all our ASF-isms Thanks On Sat, Dec 9, 2023 at 10:54 AM Etienne Jouvin wrote: > Hello all; > > Since now, I never push my extensions to any Nexus or Artifactory. > But now I must do it. > > The deploy Maven deploy is in failure and I notice it comes from the > configuration for the plugin nexus-staging-maven-plugin. > > The configuration comes from the artifact nifi, where we can find the > following configuration. > > > > org.sonatype.plugins > > nexus-staging-maven-plugin > > 1.6.13 > > true > > > > 15 > > repository.apache.org > > https://repository.apache.org/ > > > > > > > Two things : > I did not have any issue when I wanted to push my extension in SNAPSHOT > version, except I had to configure the enforcer to not fire exception > > And to be able to push my extensions in my custom Artifactory, I had to > disable it by the following configuration, in the build node at my root > pom.xml file : > > > > > > org.sonatype.plugins > > nexus-staging-maven-plugin > > > > true > > > > > > > What do you think if you put your build configuration inside a profile ? > Like this, we will not have to add a custom configuration. > > Regards > > Etienne Jouvin > >
NiFi custom extension and deploy phase on Maven
Hello all; Since now, I never push my extensions to any Nexus or Artifactory. But now I must do it. The deploy Maven deploy is in failure and I notice it comes from the configuration for the plugin nexus-staging-maven-plugin. The configuration comes from the artifact nifi, where we can find the following configuration. org.sonatype.plugins nexus-staging-maven-plugin 1.6.13 true 15 repository.apache.org https://repository.apache.org/ Two things : I did not have any issue when I wanted to push my extension in SNAPSHOT version, except I had to configure the enforcer to not fire exception And to be able to push my extensions in my custom Artifactory, I had to disable it by the following configuration, in the build node at my root pom.xml file : org.sonatype.plugins nexus-staging-maven-plugin true What do you think if you put your build configuration inside a profile ? Like this, we will not have to add a custom configuration. Regards Etienne Jouvin
