Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
+1 - pulled in the dependency changes, deleted my .m2 cache and the build
ran as expected. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/538
@mmiklavc Added a quick note, and listed those dependencies off. Let me
know if there's anything else you want in there.
---
If your project is set up for it, you can reply to this
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/538
@mmiklavc @dlyle65535 Do we want to compromise on this for now by removing
the dependency, and kick out another ticket to investigate a more robust way to
manage this?
Mike,
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
Also @mmiklavc, please remember if the intended effect was to make the rpm
build happen after everything else completed then install + pom dependencies
didn't work. If you take a close
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
fwiw, I ran a local test that seems to work fine. There must a be a subtle
difference somewhere in our build, but I haven't found it yet.
```
Maybe it is the relative parent path?
On April 20, 2017 at 20:05:31, mmiklavc (g...@git.apache.org) 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
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
As I stated in https://issues.apache.org/jira/browse/METRON-856, this is a
fix that will work given the current configuration, but will quite possibly
break with future changes. Given
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
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
The .m2 cache is an extension of the local target directories and you're
correct that upping the version to 0.4.0 caused the initial issue with missing
artifacts. Regardless of maven
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
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/538
@dlyle65535 I'm all for that. I'll update the ticket and the PR in a
little bit
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
11 matches
Mail list logo
