Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
In fact, having given it additional thought, the dependency mechanism is a
way of saying "hey Maven, make sure you pull those artifacts into our .m2
cache" which isn't really the desired result here.
We need to make sure the reactor orderer understands that we cannot build
the RPMs until we've built the other tar.gzs.
The reason it started becoming a problem was that we didn't have the 0.4.0
artifacts in our m2 cache so Maven complained. Running an install "fixed" the
issue but, we don't need them there to build the rpms, so not really a fix.
---
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.
---
