[
https://issues.apache.org/jira/browse/NIFI-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305092#comment-14305092
]
Bryan Bende commented on NIFI-316:
----------------------------------
Thanks! I was trying to think of some way to catch problems like this at build
time, so we would know the archetype still works based on any refactoring in
the code...
It looks like this might be an option:
http://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html
And the third post here:
http://stackoverflow.com/questions/4082643/how-can-i-test-a-maven-archetype-that-ive-just-created
> Update annotation package names in processor-bundle-archetype
> -------------------------------------------------------------
>
> Key: NIFI-316
> URL: https://issues.apache.org/jira/browse/NIFI-316
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 0.0.2
> Reporter: Bryan Bende
> Priority: Minor
>
> The example processor in nifi-processor-bundle-archetype needs to be updated
> to use the refactored package names for the annotations (Tags,
> CapabilityDescription, OnScheduled).
> Right now the archetype generation succeeds, but the build of a new bundle
> will fail the tests due to the old annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
