On Oct 31, 2012, at 9:18 PM, "Coarr, Matt" <[email protected]> wrote: > My understanding is this would be fine if we were running "mvn install" > instead of "mvn compile", but "mvn compile" won't be able to grab the > dependencies for components that are not being compile in the current > build (e.g. There is no jar for ctakes-type-system in the ~/.m2/repository > repo).
Note that `mvn compile` from the root cTAKES directory *will* collect all the dependencies for the cTAKES sub-modules. But you're right that if you run `mvn compile` from one of the sub-modules (e.g. ctakes-assertion) then it won't be able to find the dependencies of the sister modules. As far as I know though, Jenkins is running `mvn compile` from the top level, so that shouldn't be the issue. Steve
