nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-272) Create Maven Archetype for a Processor bundle
Date Fri, 23 Jan 2015 02:24:34 GMT


ASF GitHub Bot commented on NIFI-272:

Github user bbende commented on the pull request:
    So I was able to address the two items we discussed: 
    1. The artifactId will now be entered as the artifactId you want for the top-level artifact,
so for example "nifi-donothing-bundle". An additional property called artifactBaseName will
be specified that controls the sub-modules, in this example artifactBaseName would be set
to "donothing" if you want to produce nifi-donothing-processors and nifi-donothing-nar.
      In order to get this to work I had to abandon the modules elements in the archetype
descriptor in favor of using only filesets. The modules didn't seem to pick up the artifactBaseName
property when doing replacement on the directories.
    2. The archetype will now respect the package entered during archetype generation.
    An updated example of using the archetype is the following:
        mvn archetype:generate -DarchetypeGroupId=org.apache.nifi -DarchetypeArtifactId=nifi-processor-bundle-archetype
-DarchetypeVersion=0.0.1-incubating-SNAPSHOT -DgroupId=org.apache.nifi -DartifactId=nifi-donothing-bundle
-DartifactBaseName=donothing -Dpackage=my.test.processors -Dversion=1.0

> Create Maven Archetype for a Processor bundle
> ---------------------------------------------
>                 Key: NIFI-272
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Wish
>          Components: Tools and Build
>            Reporter: Mark Payne
> This will allow developers to very quickly and easily create a new nar, processor, parent/bundle
multi-module maven setup, rather than creating all of it by hand.

This message was sent by Atlassian JIRA

View raw message