You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mahout.apache.org by "Andrew Palumbo (Jira)" <ji...@apache.org> on 2019/11/02 11:52:00 UTC
[jira] [Commented] (MAHOUT-2075) Cross Compile and Deploy artifacts
for Scala 2.11 and 2.12
[ https://issues.apache.org/jira/browse/MAHOUT-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965324#comment-16965324 ]
Andrew Palumbo commented on MAHOUT-2075:
----------------------------------------
[https://help.sonatype.com/repomanager2/staging-releases/managing-staging-repositories]
if need be we can even drag and drop different Scala Compiled artifacts to the same staging repo, al long as they are from the same IP
> Cross Compile and Deploy artifacts for Scala 2.11 and 2.12
> ----------------------------------------------------------
>
> Key: MAHOUT-2075
> URL: https://issues.apache.org/jira/browse/MAHOUT-2075
> Project: Mahout
> Issue Type: New Feature
> Affects Versions: 0.14.0
> Reporter: Andrew Palumbo
> Assignee: Andrew Palumbo
> Priority: Critical
> Fix For: 14.1
>
>
> [~pferrel], Mahout's current largest known customer, PMC member and contributor, has need for Scala 2.11 modules . [~rawkintrevo] has created a {{change-scala-versions.sh}}. Script; we Should be easily able to If only by hand for this version, compile and deploy Scala 2.11 modules To nexus . For the next releases, we may want to consider keeping a Scala 2.11 branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)