So as you may have noticed, we just experienced the same kind of spurious build error with ctakes-relation-extractor that we were seeing with ctakes-assertion before. We got errors like:
Could not resolve dependencies for project org.apache.ctakes:ctakes-core:jar:3.1.0-incubating-SNAPSHOT: The following artifacts could not be resolved: org.apache.ctakes:ctakes-type-system:jar:3.1.0-incubating-SNAPSHOT, org.apache.ctakes:ctakes-utils:jar:3.1.0-incubating-SNAPSHOT This is exactly the error that we get if you run `mvn compile` from the `ctakes-core` directory, which we should never be doing. And there's no error if we run `mvn compile` from the top-level directory, which is what we should always be doing. So I suspect that Jenkins is somehow configured to run `mvn compile` separately for the separate modules. Can we turn that off, and only run the `mvn compile` from the top level? There should be no need to run it for each module if we run it from the top. Steve P.S. To make Jenkins happy again, all you have to do is start a build manually with the "Build Now" button in Jenkins. But we shouldn't need to do that.
