[ 
https://issues.apache.org/jira/browse/SYSTEMML-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306109#comment-15306109
 ] 

Niketan Pansare commented on SYSTEMML-704:
------------------------------------------

Alternate option is to use:
        <repository>
            <id>mavenized-jcuda-mvn-repo</id>
            
<url>https://raw.github.com/MysterionRise/mavenized-jcuda/mvn-repo/</url>
            <snapshots>
                <enabled>true</enabled>
                <updatePolicy>always</updatePolicy>
            </snapshots>
        </repository>
       ....
      <dependency>
            <groupId>org.mystic</groupId>
            <artifactId>mavenized-jcuda</artifactId>
            <version>0.7.5b</version>
            <scope>provided</scope>
      </dependency>

This is added to the PR 165 in the commit: 
https://github.com/apache/incubator-systemml/pull/165/commits/1a52bd8908773593fb8b240b38ed0e81a33ebb3f

> Host jcu*.jar libraries on mvn repo
> -----------------------------------
>
>                 Key: SYSTEMML-704
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-704
>             Project: SystemML
>          Issue Type: Task
>            Reporter: Niketan Pansare
>            Priority: Minor
>
> The PR https://github.com/apache/incubator-systemml/pull/165/ uses system 
> scope for jcu*.jar as they are not published on mvn central. Since we are 
> planning to include them into SystemML, it would be good to host them into a 
> repo we maintain and have provided scope instead. If for LICENSE or some 
> other reasons, we are not able to host them, I am fine with rejecting this 
> issue too. From jcuda's website "JCuda is published under the terms of the 
> MIT/X11 License".
> The current version depends on jcu*-0.7.5b.jar (except jcudnn-0.7.5.jar). The 
> jars are available for download from 
> http://www.jcuda.org/downloads/downloads.html. The source is available at 
> https://github.com/jcuda
> [~nakul02] [~deron] [~luciano resende]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to