ok... but this will require also reworking jenkins and CI builds... and build engineering always scared me :)
On Tue, Mar 24, 2015 at 10:54 AM, Stevo Slavic (JIRA) <[email protected]> wrote: > Stevo Slavic created MAHOUT-1654: > ------------------------------------ > > Summary: Migrate from Maven to SBT > Key: MAHOUT-1654 > URL: https://issues.apache.org/jira/browse/MAHOUT-1654 > Project: Mahout > Issue Type: Improvement > Components: build > Reporter: Stevo Slavic > Assignee: Stevo Slavic > > > Mahout modules which are Scala libraries like mahout-math-scala, > mahout-spark/mahout-spark-shell, should be published across Scala binary > versions to be usable to wider audience. At the moment this is not possible > with Maven. We need to switch to another build tool which supports this, > and SBT is most natural choice. Besides allowing us to publish Mahout Scala > libraries across Scala binary versions, it is expected that this migration > will help us mitigate/resolve other issues (to name a few, issue of > publishing javadoc/scaladoc documentation, and long standing issue of > migration to modern CLI library with sources). > > As acceptance criteria of migration success it should be defined that both > project committers and users see only improvements/benefits, everything > else that was possible and available with existing Maven build should be > possible with SBT. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
