You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "exceptionfactory (via GitHub)" <gi...@apache.org> on 2023/06/03 21:21:08 UTC

[GitHub] [nifi] exceptionfactory commented on pull request #7329: NIFI-11630 Deprecate ECMAScript Script Engine

exceptionfactory commented on PR #7329:
URL: https://github.com/apache/nifi/pull/7329#issuecomment-1575199604

   > Should we apply this PR to `main` as well, even if it will be removed before the first 2.0 release, just to make sure they're in sync at this moment? Also should we append to the property's description some generic "this is deprecated and is subject to being removed in a later release" to go along with the `DEPRECATED` addition to the display name?
   
   Thanks for the feedback @mattyb149. I was thinking that this doesn't need to be applied to the `main` branch, but as a sort of TODO marker, it could be applied to the `main` branch, and then a follow up PR can implement the removal for 2.0.
   
   I am not opposed to adding more details to the description, but as this also includes a warning for the nifi-deprecation.log, I think that will actually be a better pointer to indicate the need for making changes.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org