nanjeshramesh opened a new pull request, #11801:
URL: https://github.com/apache/nifi/pull/11801

   # Summary
   
   [NIFI-16001](https://issues.apache.org/jira/browse/NIFI-16001)
   
   Follow-up to #11735, per the review comment from @exceptionfactory.
   
   That change added a `python-unit-tests` profile to 
`nifi-python-extension-api/pom.xml` that runs the Python unit tests through the 
`exec-maven-plugin`. The review noted this adds a notable maintenance burden to 
the standard build, so this PR removes the profile. The `re.fullmatch` fix, the 
system test in `PythonProcessorIT` and the rest of #11735 are untouched.
   
   The unit test files under `src/test/python/nifiapi` are left in place and 
can still be run by hand from the module directory:
   
   ```
   PYTHONPATH=src/main/python/src python3 -m unittest discover -s 
src/test/python/nifiapi -p 'Test*.py'
   ```
   
   If you would rather drop those two files too, or move them under the 
existing `nifi-python-framework` test setup, I am happy to do either.
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue 
created
   
   ### Pull Request Tracking
   
   - [x] Pull Request title starts with Apache NiFi Jira issue number, such as 
`NIFI-00000`
   - [x] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-00000`
   
   ### Pull Request Formatting
   
   - [x] Pull Request based on current revision of the `main` branch
   - [x] Pull Request refers to a feature branch with one commit containing 
changes
   
   # Verification
   
   - [x] Build completed using `./mvnw validate` on the affected module
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to