Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/538
@justinleet Works for me. Please indicate that we have a dependency across
projects that is not shown via the dependency mechanism. Specifically, we have
a dependency on the tarballs output via these projects:
```
<dependencies>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-common</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-data-management</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-elasticsearch</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-enrichment</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-indexing</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-parsers</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-pcap-backend</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-solr</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-profiler</artifactId>
<version>${project.parent.version}</version>
</dependency>
<dependency>
<groupId>org.apache.metron</groupId>
<artifactId>metron-config</artifactId>
<version>${project.parent.version}</version>
</dependency>
</dependencies>
```
@dlyle65535 I had tried that also re: explicit jar dependency in our
project. But there's still something not quite right in our deps. The build
doesn't seem to find the artifacts even though they're in the reactor tree when
I do that. I don't think it's trying to game the dependency mechanism, as Maven
doesn't really differentiate between the artifacts and the module itself -
they're pretty tightly coupled afa Maven is concerned. But absolutely agreed
about the build order with the pom deps not having worked as intended (per your
interleaved output above). I suspect you're right about the pom declaration
behind handled differently, at least from a multi-threaded perspective. I'm
unclear if this is a bug in Maven's multi-threaded mode or intended behavior,
but we certainly don't need to deal with it here.
We should look at this further in a separate PR. While we're at it, we
might even simplify things further and remove the profiles, which are typically
used for building for different environments, not acting as virtual-modules.
---
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.
---
