Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/163#issuecomment-175186780
I had a little trouble merging the PR into the current state of master. I
was able to get the relevant parts of the contribution and can be seen here [1].
Additionally, I added TODO comments to the empty unit tests to be addressed
when incorporating NIFI-1364 [2]. The presence of the empty test indicates key
functionality that will be addressed with that ticket.
Also, I tweak the name of the profile that enables the groovy unit tests to
keep consistent with the other available profiles and added the groovy profile
to the Travis CI config.
@alopresto When running with the tests enabled, everything appears to run
successfully however, I'm seeing checksum and other warnings for
groovy-eclipse-batch. Have you seen these before?
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
e691b3c825cdd3ebbdd22017300182e953814469 for
http://repository.codehaus.org/org/codehaus/groovy/groovy-eclipse-batch/maven-metadata.xml
> [WARNING] The metadata
~/.m2/repository/org/codehaus/groovy/groovy-eclipse-batch/maven-metadata-codehaus.org.xml
is invalid: entity reference name can not contain character =' (position:
START_TAG seen
...com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=... @1:269)
Outside of these warnings everything looks good. Let me know if you seen
issues with this artifact before. Other's have asked for these capabilities
before so this is definitely a cool addition. Thanks!
[1]
https://github.com/mcgilman/nifi/commit/82919c1a0cb7b47d8e66045ed0638a992bc4b7ec
[2] https://issues.apache.org/jira/browse/NIFI-1364
---
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.
---
