Maybe it is the relative parent path?
On April 20, 2017 at 20:05:31, mmiklavc ([email protected]) wrote: Github user mmiklavc commented on the issue: https://github.com/apache/incubator-metron/pull/538 Further, the reason that install worked is not because it needs the artifacts in the cache, per se. It's because of something in the way our multi-module build is structured that isn't allowing artifacts in the metron-deployment project hierarchy to see projects in metron-platform. The reason "package" would normally work on a typical build (without ever having done an install) is because sibling modules are able to reference the pom info of each other, and therefore the appropriate target directories containing the standard build artifacts, e.g. jars. --- 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. ---
