You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Chris Herrera (JIRA)" <ji...@apache.org> on 2017/06/17 17:08:01 UTC
[jira] [Resolved] (NIFI-4083) Add a maven Archtype for the new
record-based processors
[ https://issues.apache.org/jira/browse/NIFI-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Herrera resolved NIFI-4083.
---------------------------------
Resolution: Won't Do
Assignee: Chris Herrera
Closed based on constructive feedback
For an archetype, I am on the fence about whether maintaining a separate
archetype is worth it. We could also just document the maven dependcies
that should be added to work with records when using a project generated
from the standard archetype? With that plus the abstract record processor
it might be easy enough for people to get going.
> Add a maven Archtype for the new record-based processors
> --------------------------------------------------------
>
> Key: NIFI-4083
> URL: https://issues.apache.org/jira/browse/NIFI-4083
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Reporter: Chris Herrera
> Assignee: Chris Herrera
> Priority: Minor
> Labels: beginner, starter
>
> Now that the record-based processors have been released, it would be good to have corresponding archetypes. I am thinking that this would be a separate archetype along side the standard processor vs the record processor;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)