It is expected. Malhar 3.2 was released *after* Apex 3.2 was released,
so it was not possible to refer to something that did not exist. Please
check that creating maven project with Apex 3.3 depends on Malhar
library with the correct groupId (should be org.apache.apex).
Thank you,
Vlad
On 11/19/15 03:18, Chinmay Kolhatkar wrote:
Hi,
I just noticed that when the maven project is created with apex 3.2
app-archetype, it adds malhar-library from com.datatorrent groupId as
dependency.
I've logged an jira for the same:
https://malhar.atlassian.net/browse/APEX-271
~ Chinmay.
