Github user asfgit commented on the issue:
https://github.com/apache/incubator-rya/pull/188
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/287/<h2>Build
result: ABORTED</span></h2>[...truncated 6.29 MB...][INFO]
------------------------------------------------------------------------[INFO]
Building Apache Rya PCJ Fluo Demo 3.2.11-incubating-SNAPSHOT[INFO]
------------------------------------------------------------------------[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ rya.pcj.fluo.demo
---[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy:
java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO]
[INFO] --- apache-rat-plugin:0.11:check (check-licenses) @ rya.pcj.fluo.demo
---[INFO] 51 implicit excludes (use -debug for more details).[INFO] Exclude:
**/resources/META-INF/services/**[INFO] 4 resources included (use -debug for
more details)[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0
generated: 0 approved: 4 licence.[WARNING] Failed to notify spy
hudson.maven.Mave
n3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid
object ID 12 iota=55[INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce
(enforce-mvn) @ rya.pcj.fluo.demo ---[WARNING] Failed to notify spy
hudson.maven.Maven3Builder$JenkinsEventSpy:
java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @
rya.pcj.fluo.demo ---Build was abortedAborted by mihalikchannel stoppedSetting
status of 6b669be91fad503c3a5977425959e04daab33737 to FAILURE with url
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/287/
and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing
---
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.
---
