any plans to release to maven?

[oneapi-src]

any plans to release to maven?

[dr-pain]

Thank you for your interest to DAAL and sorry for delay with answer.
release to maven is in our future plans. We will let you know when DAAL will be available in maven.

[almson]

Releasing to maven is crucial.

The worst part about the daal.jar that is bundled now is that it doesn't have javadoc. This necessitates workarounds.

Please also include libJavaApi.so in the jar. You can look at JCuda, com.github.fommil.netlib, or JavaCPP for examples how this can be done.

At the least, add a pom.xml to the source code so that it is easy to build and install locally.

[dr-pain]

Hello almson!

Please also include libJavaApi.so in the jar. You can look at JCuda, com.github.fommil.netlib, or JavaCPP for examples how this can be done.

we can not simple include libJavaApi.so into jar because: this is not single so which daal jar depend of; daal support 6 platforms (lnx/mac/win + 32bit/64bit), so all binaries somehow needs to be included into jar to continue support of these platforms.
instead of including all kind of binaries into jar, we plan to have 5 separate zip packages. daal users will be needed to download-unpack binaries thru maven-dependency-plugin. exact zip file may be choosed via profiles.

At the least, add a pom.xml to the source code so that it is easy to build and install locally.

I have attached pom.xml to this post. Could you look at it and tell us your opinion
about chosen scheme of daal at maven publishing?

pom.zip
Andrey

[almson]

Did you look at JCuda or Netlib before coming up with your own method of handling the native libraries? Because your method is worse.

They don't use java.library.path because it is a very inconvenient mechanism. At runtime, they detect what platform they're running on and extract the appropriate native library to /tmp and load it dynamically.

In the POM, JCuda uses opt-in for desired platforms:

        <dependency>
            <groupId>org.jcuda</groupId>
            <artifactId>jcudnn</artifactId>
            <version>0.9.0</version>
        </dependency>
        <dependency>
            <groupId>org.jcuda</groupId>
            <artifactId>jcudnn-natives</artifactId>
            <version>0.9.0</version>
            <classifier>linux-x86_64</classifier>
        </dependency>
        <dependency>
            <groupId>org.jcuda</groupId>
            <artifactId>jcudnn-natives</artifactId>
            <version>0.9.0</version>
            <classifier>windows-x86_64</classifier>
        </dependency>

while Netlib uses opt-out:

        <dependency>
            <groupId>com.github.fommil.netlib</groupId>
            <artifactId>all</artifactId>
            <version>1.1.2</version>
            <type>pom</type>
            <exclusions>
                <exclusion>
                    <groupId>com.github.fommil.netlib</groupId>
                    <artifactId>netlib-native_ref-linux-armhf</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.github.fommil.netlib</groupId>
                    <artifactId>netlib-native_ref-linux-i686</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.github.fommil.netlib</groupId>
                    <artifactId>netlib-native_ref-win-i686</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.github.fommil.netlib</groupId>
                    <artifactId>netlib-native_system-linux-armhf</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.github.fommil.netlib</groupId>
                    <artifactId>netlib-native_system-linux-i686</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.github.fommil.netlib</groupId>
                    <artifactId>netlib-native_system-win-i686</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

[dr-pain]

Hello almson!

thank you for pointing us to jcuda. I have looked at at their implementation and it looks really better than my proposal (from customers point of view). I need to finish some experiments, but looks like we will use the same approach in DAAL.

Andrey

PS: I considered packaging DAAL binaries into jar (instead of zip), but missed some key details.

[dr-pain]

Hello almson!

We have published DAAL at maven central today. Repository address is http://central.maven.org/maven2/com/intel/daal.
To use DAAL in maven projects just add following dependency into .pom file:
<dependency>
<groupId>com.intel.daal</groupId>
<artifactId>daal</artifactId>
<version>2019.0.001</version>
</dependency>

Andrey