You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Stevo Slavic (JIRA)" <ji...@apache.org> on 2015/03/24 18:54:53 UTC
[jira] [Created] (MAHOUT-1654) Migrate from Maven to SBT
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)
Re: [jira] [Created] (MAHOUT-1654) Migrate from Maven to SBT
Posted by Stevo Slavić <ss...@gmail.com>.
Hello Dmitriy,
Jenkins should be a no-brainer, nothing fundamentally different from Maven
in that regard. Will add subtasks to JIRA, including task for updating of
Jenkins build definitions. During WIP they can be new/separate build
job(s). I'm not scared of build engineering, but don't have appropriate
access rights on https://builds.apache.org/ to make work easier, e.g.
cannot create new job or edit existing Mahout jobs - that would make work
easier. Maybe just infra can create separate job(s) for me to work on this
migration.
One concern (time/effort wise) I have is the custom maven plugin we have
for collections code generation, equivalent has to be made available for
sbt, or some other solution found. Never liked that the code generation was
running on every build, over and over again; maybe that can be improved.
Kind regards
Stevo Slavic.
On Tue, Mar 24, 2015 at 7:22 PM, Dmitriy Lyubimov <dl...@gmail.com> wrote:
> 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) <ji...@apache.org>
> 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)
> >
>
Re: [jira] [Created] (MAHOUT-1654) Migrate from Maven to SBT
Posted by Dmitriy Lyubimov <dl...@gmail.com>.
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) <ji...@apache.org>
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)
>