Right. In 0.0.2 we moved around the annotations and deprecated the old ones. We did this because they were all in a package called “org.apache.nifi.processor.annotations” or something like that, and the annotations really should apply to Reporting Tasks and Controller Services, as well, as they are becoming more first-class citizens of the framework.
The code that Dan wrote is intended to run against the new annotations. As such, I decided it probably made sense to go ahead and wait until the 0.1.0 release to pull that in. Code review looked good though, and I think it’s ready to go - just holding off because of the annotation changes. THanks -Mark From: danbress Sent: Wednesday, February 18, 2015 7:47 AM To: [email protected] Github user danbress commented on the pull request: https://github.com/apache/incubator-nifi/pull/28#issuecomment-74858249 Regarding generated processor documentation:I think everything is ready to go. When I spoke to Mark about this last week he said he was keeping this on the side until the 0.0.2 release was cut. So once 0.0.2 is cut, the auto doc feature will get merged into 0.1.0 Dan On Wed, Feb 18, 2015 at 12:12 AM, asfbot <[email protected]> wrote: > Joe Witt on [email protected] replies: > Aldrin: > > I agree with your understanding for the ASL/MIT licensing. If we do > that we will need to update our licensings to reflect the source > dependency but that is no problem at all. I definitely think it is > worth it if we can bypass exception handling as a routine flow control > mechanism. > > Thanks! > Joe > 9 > r the next few days. > , it looks like there may be a way around the exceptions. Since the librar= > y in question is ASL/MIT, it's my understanding that it is okay to > reproduc= > e code segments as these fall in Category A, is this correct? > king for a way to utilize output streams, but JsonPath does not currently > p= > rovide this. > ur > e > se > > — > Reply to this email directly or view it on GitHub > <https://github.com/apache/incubator-nifi/pull/28#issuecomment-74813584>. > --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at [email protected] or file a JIRA ticket with INFRA. ---
