Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Stevo Slavić <ss...@gmail.com>]

Hello Apache Mahout developers,

Several Apache Mahout build jobs are failing, they are configured to run
with Apache Maven 2, while pom.xml has recently been changed to require
Apache Maven 3. To fix this it's enough to update configuration of these
jobs, so they use Apache Maven 3 to execute.

While at it, please also configure mahout-nightly job to deploy/release
distribution archive, by appending:

-Dmahout.skip.distribution=false

to the Maven goals of the job. I think this will be useful, Mahout beginner
which wants to use latest algorithms, will not have to build Mahout
herself, to get nicely packaged distribution of Apache Mahout from Apache
snapshots repository like
https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/

Current Maven goals for mahout-nightly job are "clean install deploy". That
"install" is redundant, it's implied because of "deploy", both of these
phases are in same, default lifecycle, executing up to deploy will run
through install phase as well.

Kind regards,
Stevo Slavić.

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Ted Dunning <te...@gmail.com>]

Works as far as I can tell.

The job to update the repo is started, but there seems to be a fairly
up-to-date version of 0.8 snapshot on the apache repo already that seems to
work fine.




On Mon, May 27, 2013 at 3:09 PM, Stevo Slavić <ss...@gmail.com> wrote:

> Binaries of individual Mahout modules are already being published by
> mahout-nightly job to Apache snapshots repository, e.g. see
>
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-core/0.8-SNAPSHOT/
>
> To try Mahout 0.8-SNAPSHOT modules in an new or existing Mahout powered app
> or service (even without distribution module published) one can define in
> pom.xml a repository like:
>
> ...
> <repository>
>   <id>apache.snapshots</id>
>   <url>https://repository.apache.org/content/groups/snapshots</url>
>   <releases><enabled>false</enabled></releases>
>   <snapshots>
>     <enabled>true</enabled>
>     <updatePolicy>daily</updatePolicy>
>   </snapshots>
> </repository>
> ...
>
> then define Mahout modules dependency to version 0.8-SNAPSHOT and use them.
>
>
> Once that switch is added to the Maven goals of mahout-nightly build job,
> it will also publish Mahout distribution archives (zip, tar.gz, tar.bz2,
> src and binaries bundles) to Apache snapshots repository at
>
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
>
> From there e.g. a MiA reader can download and unpack appropriate archive
> (zip, tar.gz, or tar.bz2 binaries), configure MAHOUT_HOME environment
> variable to point to unpacked directory and then run Mahout commands & try
> examples.
>
>
>
>
> On Mon, May 27, 2013 at 11:35 PM, Ted Dunning <te...@gmail.com>
> wrote:
>
> > This is a good idea to publish the snapshots.  It would definitely
> simplify
> > bleeding edge projects.
> >
> > I have tried putting this onto the mahout-nightly job.
> >
> > What special pom invocation is required to consume these artifacts?
> >
> >
> > On Mon, May 27, 2013 at 11:09 AM, Stevo Slavić <ss...@gmail.com>
> wrote:
> >
> > > Nice I see builds are running, past Maven version check.
> > >
> > > What do you all think about my second suggestion - to enable
> > mahout-nightly
> > > job to publish distribution archives on apache snapshots repository?
> One
> > > more advantage of this would be to have publishing mechanism tested in
> at
> > > least one CI build job.
> > > To do this, one has to configure mahout-nightly job, append "
> > > -Dmahout.skip.distribution=false" to Maven build goals.
> > >
> > >
> > > On Mon, May 27, 2013 at 7:50 PM, Ted Dunning <te...@gmail.com>
> > > wrote:
> > >
> > > > I changed all the Mahout projects I could find.
> > > >
> > > > I also deleted MahoutQM since it hadn't been run since 2010
> > > >
> > > >
> > > > On Mon, May 27, 2013 at 5:21 AM, Sean Owen <sr...@gmail.com> wrote:
> > > >
> > > > > That's a great description, thanks. I logged in to Jenkins, and I
> do
> > > not
> > > > > see a Configure link, so I likely do not have rights. I don't know
> > who
> > > > > does?
> > > > >
> > > > >
> > > > > On Mon, May 27, 2013 at 12:41 PM, Stevo Slavić <ss...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > +1 for enforcing Maven 3, it's more strict so will check and
> report
> > > > > issues
> > > > > > with build script, and newer versions of plugins require it or
> just
> > > > work
> > > > > > and are tested with it.
> > > > > >
> > > > > > Go to each job (e.g.
> https://builds.apache.org/job/mahout-nightly/
> > ),
> > > > > and
> > > > > > if you have access/rights click on Configure link; then in Build
> > > > section,
> > > > > > there should be "Maven Version" drop-down, with hopefully some
> > Maven
> > > 3
> > > > > > option in it. Click Save or Apply.
> > > > > > Check on the same page, if there are some prebuild/postbuild
> steps
> > > > which
> > > > > > run maven, they also need to be configured to use Maven 3.
> > > > > >
> > > > > > If nobody has appropriate access rights, maybe create support
> > ticket
> > > on
> > > > > > INFRA.
> > > > > >
> > > > > > Kind regards,
> > > > > > Stevo Slavić.
> > > > > >
> > > > > >
> > > > > > On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > (I snuck in this Maven requirement with some other updates to
> > > > plugins.
> > > > > I
> > > > > > > think it is not strictly essential for the other plugins, so
> > could
> > > be
> > > > > > > reverted. But Maven 3 has been out for nearly 3 years, and
> surely
> > > > > Apache
> > > > > > > itself should use it now. But I don't know how to configure
> these
> > > > jobs
> > > > > to
> > > > > > > run with 3 vs 2.)
> > > > > > >
> > > > > > >
> > > > > > > On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <
> sslavic@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Hello Apache Mahout developers,
> > > > > > > >
> > > > > > > > Several Apache Mahout build jobs are failing, they are
> > configured
> > > > to
> > > > > > run
> > > > > > > > with Apache Maven 2, while pom.xml has recently been changed
> to
> > > > > require
> > > > > > > > Apache Maven 3. To fix this it's enough to update
> configuration
> > > of
> > > > > > these
> > > > > > > > jobs, so they use Apache Maven 3 to execute.
> > > > > > > >
> > > > > > > > While at it, please also configure mahout-nightly job to
> > > > > deploy/release
> > > > > > > > distribution archive, by appending:
> > > > > > > >
> > > > > > > > -Dmahout.skip.distribution=false
> > > > > > > >
> > > > > > > > to the Maven goals of the job. I think this will be useful,
> > > Mahout
> > > > > > > beginner
> > > > > > > > which wants to use latest algorithms, will not have to build
> > > Mahout
> > > > > > > > herself, to get nicely packaged distribution of Apache Mahout
> > > from
> > > > > > Apache
> > > > > > > > snapshots repository like
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> > > > > > > >
> > > > > > > > Current Maven goals for mahout-nightly job are "clean install
> > > > > deploy".
> > > > > > > That
> > > > > > > > "install" is redundant, it's implied because of "deploy",
> both
> > of
> > > > > these
> > > > > > > > phases are in same, default lifecycle, executing up to deploy
> > > will
> > > > > run
> > > > > > > > through install phase as well.
> > > > > > > >
> > > > > > > > Kind regards,
> > > > > > > > Stevo Slavić.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Stevo Slavić <ss...@gmail.com>]

Binaries of individual Mahout modules are already being published by
mahout-nightly job to Apache snapshots repository, e.g. see
https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-core/0.8-SNAPSHOT/

To try Mahout 0.8-SNAPSHOT modules in an new or existing Mahout powered app
or service (even without distribution module published) one can define in
pom.xml a repository like:

...
<repository>
  <id>apache.snapshots</id>
  <url>https://repository.apache.org/content/groups/snapshots</url>
  <releases><enabled>false</enabled></releases>
  <snapshots>
    <enabled>true</enabled>
    <updatePolicy>daily</updatePolicy>
  </snapshots>
</repository>
...

then define Mahout modules dependency to version 0.8-SNAPSHOT and use them.


Once that switch is added to the Maven goals of mahout-nightly build job,
it will also publish Mahout distribution archives (zip, tar.gz, tar.bz2,
src and binaries bundles) to Apache snapshots repository at
https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/

>From there e.g. a MiA reader can download and unpack appropriate archive
(zip, tar.gz, or tar.bz2 binaries), configure MAHOUT_HOME environment
variable to point to unpacked directory and then run Mahout commands & try
examples.




On Mon, May 27, 2013 at 11:35 PM, Ted Dunning <te...@gmail.com> wrote:

> This is a good idea to publish the snapshots.  It would definitely simplify
> bleeding edge projects.
>
> I have tried putting this onto the mahout-nightly job.
>
> What special pom invocation is required to consume these artifacts?
>
>
> On Mon, May 27, 2013 at 11:09 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
> > Nice I see builds are running, past Maven version check.
> >
> > What do you all think about my second suggestion - to enable
> mahout-nightly
> > job to publish distribution archives on apache snapshots repository? One
> > more advantage of this would be to have publishing mechanism tested in at
> > least one CI build job.
> > To do this, one has to configure mahout-nightly job, append "
> > -Dmahout.skip.distribution=false" to Maven build goals.
> >
> >
> > On Mon, May 27, 2013 at 7:50 PM, Ted Dunning <te...@gmail.com>
> > wrote:
> >
> > > I changed all the Mahout projects I could find.
> > >
> > > I also deleted MahoutQM since it hadn't been run since 2010
> > >
> > >
> > > On Mon, May 27, 2013 at 5:21 AM, Sean Owen <sr...@gmail.com> wrote:
> > >
> > > > That's a great description, thanks. I logged in to Jenkins, and I do
> > not
> > > > see a Configure link, so I likely do not have rights. I don't know
> who
> > > > does?
> > > >
> > > >
> > > > On Mon, May 27, 2013 at 12:41 PM, Stevo Slavić <ss...@gmail.com>
> > > wrote:
> > > >
> > > > > +1 for enforcing Maven 3, it's more strict so will check and report
> > > > issues
> > > > > with build script, and newer versions of plugins require it or just
> > > work
> > > > > and are tested with it.
> > > > >
> > > > > Go to each job (e.g. https://builds.apache.org/job/mahout-nightly/
> ),
> > > > and
> > > > > if you have access/rights click on Configure link; then in Build
> > > section,
> > > > > there should be "Maven Version" drop-down, with hopefully some
> Maven
> > 3
> > > > > option in it. Click Save or Apply.
> > > > > Check on the same page, if there are some prebuild/postbuild steps
> > > which
> > > > > run maven, they also need to be configured to use Maven 3.
> > > > >
> > > > > If nobody has appropriate access rights, maybe create support
> ticket
> > on
> > > > > INFRA.
> > > > >
> > > > > Kind regards,
> > > > > Stevo Slavić.
> > > > >
> > > > >
> > > > > On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com>
> > wrote:
> > > > >
> > > > > > (I snuck in this Maven requirement with some other updates to
> > > plugins.
> > > > I
> > > > > > think it is not strictly essential for the other plugins, so
> could
> > be
> > > > > > reverted. But Maven 3 has been out for nearly 3 years, and surely
> > > > Apache
> > > > > > itself should use it now. But I don't know how to configure these
> > > jobs
> > > > to
> > > > > > run with 3 vs 2.)
> > > > > >
> > > > > >
> > > > > > On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <sslavic@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > Hello Apache Mahout developers,
> > > > > > >
> > > > > > > Several Apache Mahout build jobs are failing, they are
> configured
> > > to
> > > > > run
> > > > > > > with Apache Maven 2, while pom.xml has recently been changed to
> > > > require
> > > > > > > Apache Maven 3. To fix this it's enough to update configuration
> > of
> > > > > these
> > > > > > > jobs, so they use Apache Maven 3 to execute.
> > > > > > >
> > > > > > > While at it, please also configure mahout-nightly job to
> > > > deploy/release
> > > > > > > distribution archive, by appending:
> > > > > > >
> > > > > > > -Dmahout.skip.distribution=false
> > > > > > >
> > > > > > > to the Maven goals of the job. I think this will be useful,
> > Mahout
> > > > > > beginner
> > > > > > > which wants to use latest algorithms, will not have to build
> > Mahout
> > > > > > > herself, to get nicely packaged distribution of Apache Mahout
> > from
> > > > > Apache
> > > > > > > snapshots repository like
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> > > > > > >
> > > > > > > Current Maven goals for mahout-nightly job are "clean install
> > > > deploy".
> > > > > > That
> > > > > > > "install" is redundant, it's implied because of "deploy", both
> of
> > > > these
> > > > > > > phases are in same, default lifecycle, executing up to deploy
> > will
> > > > run
> > > > > > > through install phase as well.
> > > > > > >
> > > > > > > Kind regards,
> > > > > > > Stevo Slavić.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Ted Dunning <te...@gmail.com>]

This is a good idea to publish the snapshots.  It would definitely simplify
bleeding edge projects.

I have tried putting this onto the mahout-nightly job.

What special pom invocation is required to consume these artifacts?


On Mon, May 27, 2013 at 11:09 AM, Stevo Slavić <ss...@gmail.com> wrote:

> Nice I see builds are running, past Maven version check.
>
> What do you all think about my second suggestion - to enable mahout-nightly
> job to publish distribution archives on apache snapshots repository? One
> more advantage of this would be to have publishing mechanism tested in at
> least one CI build job.
> To do this, one has to configure mahout-nightly job, append "
> -Dmahout.skip.distribution=false" to Maven build goals.
>
>
> On Mon, May 27, 2013 at 7:50 PM, Ted Dunning <te...@gmail.com>
> wrote:
>
> > I changed all the Mahout projects I could find.
> >
> > I also deleted MahoutQM since it hadn't been run since 2010
> >
> >
> > On Mon, May 27, 2013 at 5:21 AM, Sean Owen <sr...@gmail.com> wrote:
> >
> > > That's a great description, thanks. I logged in to Jenkins, and I do
> not
> > > see a Configure link, so I likely do not have rights. I don't know who
> > > does?
> > >
> > >
> > > On Mon, May 27, 2013 at 12:41 PM, Stevo Slavić <ss...@gmail.com>
> > wrote:
> > >
> > > > +1 for enforcing Maven 3, it's more strict so will check and report
> > > issues
> > > > with build script, and newer versions of plugins require it or just
> > work
> > > > and are tested with it.
> > > >
> > > > Go to each job (e.g. https://builds.apache.org/job/mahout-nightly/),
> > > and
> > > > if you have access/rights click on Configure link; then in Build
> > section,
> > > > there should be "Maven Version" drop-down, with hopefully some Maven
> 3
> > > > option in it. Click Save or Apply.
> > > > Check on the same page, if there are some prebuild/postbuild steps
> > which
> > > > run maven, they also need to be configured to use Maven 3.
> > > >
> > > > If nobody has appropriate access rights, maybe create support ticket
> on
> > > > INFRA.
> > > >
> > > > Kind regards,
> > > > Stevo Slavić.
> > > >
> > > >
> > > > On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com>
> wrote:
> > > >
> > > > > (I snuck in this Maven requirement with some other updates to
> > plugins.
> > > I
> > > > > think it is not strictly essential for the other plugins, so could
> be
> > > > > reverted. But Maven 3 has been out for nearly 3 years, and surely
> > > Apache
> > > > > itself should use it now. But I don't know how to configure these
> > jobs
> > > to
> > > > > run with 3 vs 2.)
> > > > >
> > > > >
> > > > > On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <ss...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Hello Apache Mahout developers,
> > > > > >
> > > > > > Several Apache Mahout build jobs are failing, they are configured
> > to
> > > > run
> > > > > > with Apache Maven 2, while pom.xml has recently been changed to
> > > require
> > > > > > Apache Maven 3. To fix this it's enough to update configuration
> of
> > > > these
> > > > > > jobs, so they use Apache Maven 3 to execute.
> > > > > >
> > > > > > While at it, please also configure mahout-nightly job to
> > > deploy/release
> > > > > > distribution archive, by appending:
> > > > > >
> > > > > > -Dmahout.skip.distribution=false
> > > > > >
> > > > > > to the Maven goals of the job. I think this will be useful,
> Mahout
> > > > > beginner
> > > > > > which wants to use latest algorithms, will not have to build
> Mahout
> > > > > > herself, to get nicely packaged distribution of Apache Mahout
> from
> > > > Apache
> > > > > > snapshots repository like
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> > > > > >
> > > > > > Current Maven goals for mahout-nightly job are "clean install
> > > deploy".
> > > > > That
> > > > > > "install" is redundant, it's implied because of "deploy", both of
> > > these
> > > > > > phases are in same, default lifecycle, executing up to deploy
> will
> > > run
> > > > > > through install phase as well.
> > > > > >
> > > > > > Kind regards,
> > > > > > Stevo Slavić.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Stevo Slavić <ss...@gmail.com>]

Nice I see builds are running, past Maven version check.

What do you all think about my second suggestion - to enable mahout-nightly
job to publish distribution archives on apache snapshots repository? One
more advantage of this would be to have publishing mechanism tested in at
least one CI build job.
To do this, one has to configure mahout-nightly job, append "
-Dmahout.skip.distribution=false" to Maven build goals.


On Mon, May 27, 2013 at 7:50 PM, Ted Dunning <te...@gmail.com> wrote:

> I changed all the Mahout projects I could find.
>
> I also deleted MahoutQM since it hadn't been run since 2010
>
>
> On Mon, May 27, 2013 at 5:21 AM, Sean Owen <sr...@gmail.com> wrote:
>
> > That's a great description, thanks. I logged in to Jenkins, and I do not
> > see a Configure link, so I likely do not have rights. I don't know who
> > does?
> >
> >
> > On Mon, May 27, 2013 at 12:41 PM, Stevo Slavić <ss...@gmail.com>
> wrote:
> >
> > > +1 for enforcing Maven 3, it's more strict so will check and report
> > issues
> > > with build script, and newer versions of plugins require it or just
> work
> > > and are tested with it.
> > >
> > > Go to each job (e.g. https://builds.apache.org/job/mahout-nightly/ ),
> > and
> > > if you have access/rights click on Configure link; then in Build
> section,
> > > there should be "Maven Version" drop-down, with hopefully some Maven 3
> > > option in it. Click Save or Apply.
> > > Check on the same page, if there are some prebuild/postbuild steps
> which
> > > run maven, they also need to be configured to use Maven 3.
> > >
> > > If nobody has appropriate access rights, maybe create support ticket on
> > > INFRA.
> > >
> > > Kind regards,
> > > Stevo Slavić.
> > >
> > >
> > > On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
> > >
> > > > (I snuck in this Maven requirement with some other updates to
> plugins.
> > I
> > > > think it is not strictly essential for the other plugins, so could be
> > > > reverted. But Maven 3 has been out for nearly 3 years, and surely
> > Apache
> > > > itself should use it now. But I don't know how to configure these
> jobs
> > to
> > > > run with 3 vs 2.)
> > > >
> > > >
> > > > On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <ss...@gmail.com>
> > wrote:
> > > >
> > > > > Hello Apache Mahout developers,
> > > > >
> > > > > Several Apache Mahout build jobs are failing, they are configured
> to
> > > run
> > > > > with Apache Maven 2, while pom.xml has recently been changed to
> > require
> > > > > Apache Maven 3. To fix this it's enough to update configuration of
> > > these
> > > > > jobs, so they use Apache Maven 3 to execute.
> > > > >
> > > > > While at it, please also configure mahout-nightly job to
> > deploy/release
> > > > > distribution archive, by appending:
> > > > >
> > > > > -Dmahout.skip.distribution=false
> > > > >
> > > > > to the Maven goals of the job. I think this will be useful, Mahout
> > > > beginner
> > > > > which wants to use latest algorithms, will not have to build Mahout
> > > > > herself, to get nicely packaged distribution of Apache Mahout from
> > > Apache
> > > > > snapshots repository like
> > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> > > > >
> > > > > Current Maven goals for mahout-nightly job are "clean install
> > deploy".
> > > > That
> > > > > "install" is redundant, it's implied because of "deploy", both of
> > these
> > > > > phases are in same, default lifecycle, executing up to deploy will
> > run
> > > > > through install phase as well.
> > > > >
> > > > > Kind regards,
> > > > > Stevo Slavić.
> > > > >
> > > >
> > >
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Ted Dunning <te...@gmail.com>]

I changed all the Mahout projects I could find.

I also deleted MahoutQM since it hadn't been run since 2010


On Mon, May 27, 2013 at 5:21 AM, Sean Owen <sr...@gmail.com> wrote:

> That's a great description, thanks. I logged in to Jenkins, and I do not
> see a Configure link, so I likely do not have rights. I don't know who
> does?
>
>
> On Mon, May 27, 2013 at 12:41 PM, Stevo Slavić <ss...@gmail.com> wrote:
>
> > +1 for enforcing Maven 3, it's more strict so will check and report
> issues
> > with build script, and newer versions of plugins require it or just work
> > and are tested with it.
> >
> > Go to each job (e.g. https://builds.apache.org/job/mahout-nightly/ ),
> and
> > if you have access/rights click on Configure link; then in Build section,
> > there should be "Maven Version" drop-down, with hopefully some Maven 3
> > option in it. Click Save or Apply.
> > Check on the same page, if there are some prebuild/postbuild steps which
> > run maven, they also need to be configured to use Maven 3.
> >
> > If nobody has appropriate access rights, maybe create support ticket on
> > INFRA.
> >
> > Kind regards,
> > Stevo Slavić.
> >
> >
> > On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
> >
> > > (I snuck in this Maven requirement with some other updates to plugins.
> I
> > > think it is not strictly essential for the other plugins, so could be
> > > reverted. But Maven 3 has been out for nearly 3 years, and surely
> Apache
> > > itself should use it now. But I don't know how to configure these jobs
> to
> > > run with 3 vs 2.)
> > >
> > >
> > > On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <ss...@gmail.com>
> wrote:
> > >
> > > > Hello Apache Mahout developers,
> > > >
> > > > Several Apache Mahout build jobs are failing, they are configured to
> > run
> > > > with Apache Maven 2, while pom.xml has recently been changed to
> require
> > > > Apache Maven 3. To fix this it's enough to update configuration of
> > these
> > > > jobs, so they use Apache Maven 3 to execute.
> > > >
> > > > While at it, please also configure mahout-nightly job to
> deploy/release
> > > > distribution archive, by appending:
> > > >
> > > > -Dmahout.skip.distribution=false
> > > >
> > > > to the Maven goals of the job. I think this will be useful, Mahout
> > > beginner
> > > > which wants to use latest algorithms, will not have to build Mahout
> > > > herself, to get nicely packaged distribution of Apache Mahout from
> > Apache
> > > > snapshots repository like
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> > > >
> > > > Current Maven goals for mahout-nightly job are "clean install
> deploy".
> > > That
> > > > "install" is redundant, it's implied because of "deploy", both of
> these
> > > > phases are in same, default lifecycle, executing up to deploy will
> run
> > > > through install phase as well.
> > > >
> > > > Kind regards,
> > > > Stevo Slavić.
> > > >
> > >
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Sean Owen <sr...@gmail.com>]

That's a great description, thanks. I logged in to Jenkins, and I do not
see a Configure link, so I likely do not have rights. I don't know who does?


On Mon, May 27, 2013 at 12:41 PM, Stevo Slavić <ss...@gmail.com> wrote:

> +1 for enforcing Maven 3, it's more strict so will check and report issues
> with build script, and newer versions of plugins require it or just work
> and are tested with it.
>
> Go to each job (e.g. https://builds.apache.org/job/mahout-nightly/ ), and
> if you have access/rights click on Configure link; then in Build section,
> there should be "Maven Version" drop-down, with hopefully some Maven 3
> option in it. Click Save or Apply.
> Check on the same page, if there are some prebuild/postbuild steps which
> run maven, they also need to be configured to use Maven 3.
>
> If nobody has appropriate access rights, maybe create support ticket on
> INFRA.
>
> Kind regards,
> Stevo Slavić.
>
>
> On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
>
> > (I snuck in this Maven requirement with some other updates to plugins. I
> > think it is not strictly essential for the other plugins, so could be
> > reverted. But Maven 3 has been out for nearly 3 years, and surely Apache
> > itself should use it now. But I don't know how to configure these jobs to
> > run with 3 vs 2.)
> >
> >
> > On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <ss...@gmail.com> wrote:
> >
> > > Hello Apache Mahout developers,
> > >
> > > Several Apache Mahout build jobs are failing, they are configured to
> run
> > > with Apache Maven 2, while pom.xml has recently been changed to require
> > > Apache Maven 3. To fix this it's enough to update configuration of
> these
> > > jobs, so they use Apache Maven 3 to execute.
> > >
> > > While at it, please also configure mahout-nightly job to deploy/release
> > > distribution archive, by appending:
> > >
> > > -Dmahout.skip.distribution=false
> > >
> > > to the Maven goals of the job. I think this will be useful, Mahout
> > beginner
> > > which wants to use latest algorithms, will not have to build Mahout
> > > herself, to get nicely packaged distribution of Apache Mahout from
> Apache
> > > snapshots repository like
> > >
> > >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> > >
> > > Current Maven goals for mahout-nightly job are "clean install deploy".
> > That
> > > "install" is redundant, it's implied because of "deploy", both of these
> > > phases are in same, default lifecycle, executing up to deploy will run
> > > through install phase as well.
> > >
> > > Kind regards,
> > > Stevo Slavić.
> > >
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Stevo Slavić <ss...@gmail.com>]

+1 for enforcing Maven 3, it's more strict so will check and report issues
with build script, and newer versions of plugins require it or just work
and are tested with it.

Go to each job (e.g. https://builds.apache.org/job/mahout-nightly/ ), and
if you have access/rights click on Configure link; then in Build section,
there should be "Maven Version" drop-down, with hopefully some Maven 3
option in it. Click Save or Apply.
Check on the same page, if there are some prebuild/postbuild steps which
run maven, they also need to be configured to use Maven 3.

If nobody has appropriate access rights, maybe create support ticket on
INFRA.

Kind regards,
Stevo Slavić.


On Mon, May 27, 2013 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:

> (I snuck in this Maven requirement with some other updates to plugins. I
> think it is not strictly essential for the other plugins, so could be
> reverted. But Maven 3 has been out for nearly 3 years, and surely Apache
> itself should use it now. But I don't know how to configure these jobs to
> run with 3 vs 2.)
>
>
> On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
> > Hello Apache Mahout developers,
> >
> > Several Apache Mahout build jobs are failing, they are configured to run
> > with Apache Maven 2, while pom.xml has recently been changed to require
> > Apache Maven 3. To fix this it's enough to update configuration of these
> > jobs, so they use Apache Maven 3 to execute.
> >
> > While at it, please also configure mahout-nightly job to deploy/release
> > distribution archive, by appending:
> >
> > -Dmahout.skip.distribution=false
> >
> > to the Maven goals of the job. I think this will be useful, Mahout
> beginner
> > which wants to use latest algorithms, will not have to build Mahout
> > herself, to get nicely packaged distribution of Apache Mahout from Apache
> > snapshots repository like
> >
> >
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
> >
> > Current Maven goals for mahout-nightly job are "clean install deploy".
> That
> > "install" is redundant, it's implied because of "deploy", both of these
> > phases are in same, default lifecycle, executing up to deploy will run
> > through install phase as well.
> >
> > Kind regards,
> > Stevo Slavić.
> >
>

Re: Req: Configure Maven 3 in CI jobs, and enable distribution snapshot deploy

[Sean Owen <sr...@gmail.com>]

(I snuck in this Maven requirement with some other updates to plugins. I
think it is not strictly essential for the other plugins, so could be
reverted. But Maven 3 has been out for nearly 3 years, and surely Apache
itself should use it now. But I don't know how to configure these jobs to
run with 3 vs 2.)


On Mon, May 27, 2013 at 1:39 AM, Stevo Slavić <ss...@gmail.com> wrote:

> Hello Apache Mahout developers,
>
> Several Apache Mahout build jobs are failing, they are configured to run
> with Apache Maven 2, while pom.xml has recently been changed to require
> Apache Maven 3. To fix this it's enough to update configuration of these
> jobs, so they use Apache Maven 3 to execute.
>
> While at it, please also configure mahout-nightly job to deploy/release
> distribution archive, by appending:
>
> -Dmahout.skip.distribution=false
>
> to the Maven goals of the job. I think this will be useful, Mahout beginner
> which wants to use latest algorithms, will not have to build Mahout
> herself, to get nicely packaged distribution of Apache Mahout from Apache
> snapshots repository like
>
> https://repository.apache.org/content/groups/snapshots/org/apache/mahout/mahout-distribution/0.8-SNAPSHOT/
>
> Current Maven goals for mahout-nightly job are "clean install deploy". That
> "install" is redundant, it's implied because of "deploy", both of these
> phases are in same, default lifecycle, executing up to deploy will run
> through install phase as well.
>
> Kind regards,
> Stevo Slavić.
>