Hi Max,
I just tested a build using gradle (with your build.gradle file) and some
flink-ml algorithms. And it was completed without the problem of the
unresolved breeze dependency.
I use the version 2.2.1 of Gradle. Which version are you using?
Since you’re using Flink’s snapshots and have
Hmm then I assume that version 2 can properly handle maven property
variables.
On Thu, Jun 11, 2015 at 3:05 PM Maximilian Alber alber.maximil...@gmail.com
wrote:
Hi Till,
I use the standard one for Ubuntu 15.04, which is 1.5.
That did not make any difference.
Thanks and Cheers,
Max
On
Well then, I should update ;-)
On Thu, Jun 11, 2015 at 4:01 PM, Till Rohrmann till.rohrm...@gmail.com
wrote:
Hmm then I assume that version 2 can properly handle maven property
variables.
On Thu, Jun 11, 2015 at 3:05 PM Maximilian Alber
alber.maximil...@gmail.com wrote:
Hi Till,
I use
Hi Till,
Thanks for the quick help!
Cheers,
Max
On Wed, Jun 10, 2015 at 5:50 PM, Till Rohrmann till.rohrm...@gmail.com
wrote:
Hi Max,
I think the reason is that the flink-ml pom contains as a dependency an
artifact with artifactId breeze_${scala.binary.version}. The variable
Hi Max,
I think the reason is that the flink-ml pom contains as a dependency an
artifact with artifactId breeze_${scala.binary.version}. The variable
scala.binary.version is defined in the parent pom and not substituted when
flink-ml is installed. Therefore gradle tries to find a dependency with
