Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/710
@trixpan I can't say I am in favor of it given the fact that JavaMail
Properties is a distinct part of Java Mail API and there are quite a number of
them, so the question is how do you choose which once are more essential then
others and what should their default values be if exposed as top level
properties of a Processor? These are all tough questions to answer especially
in the early stages of the processor development when we didn't really have a
chance to analyze how it's been used and what are the common suggestions from
users.
So what I would propose is to add a note to CapabilityDescription that
"additional JavaMail properties should be set as Dynamic Properties". What do
you think?
---
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.
---
