mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Which maven command to use to put all the binaries into the distribution layout?
Date Sat, 07 May 2011 21:40:49 GMT
I just tried

   mvn -DskipTests -Prelease,mahout_release package

and got the distribution artifacts in distribution/target

I also got a warning about the mahout_release profile.  I am trying it again
with just -Prelease

On Sat, May 7, 2011 at 2:21 PM, Jake Mannix <jake.mannix@gmail.com> wrote:

> I think what Xiaobo wants is something totally reasonable:
>
> we have, on the website, a full distribution, in .zip, .gz, and .bz2
> formats.  He wants to be able to produce a -SNAPSHOT form of
> this as well, from trunk checkouts.
>
> I've tried this with mvn -Prelease (requires gpg keys),
> mvn release:prepare (fails with some
>
> [INFO] [INFO] --- maven-gpg-plugin:1.1:sign (default) @ mahout ---
> [INFO] /bin/sh: gpg: command not found
>
> error), and so on.
>
> mvn package just produces jars and stuff, but doesn't zip it all
> up in a coherent distribution layout.
>
> Do we not have a "build snapshot distribution" mvn target?
>
>  -jake
>
> On Sat, May 7, 2011 at 6:41 AM, Sean Owen <srowen@gmail.com> wrote:
>
> > It sounds like you want to write your own Maven release target to
> > create the output you're looking for. Otherwise, yes this is what you
> > need to do. 'package' is the right target as far as the project is
> > concerned, and yes you can write a script like this to assemble
> > whatever you want. That's also an option.
> >
> > What is missing? not clear what you mean.
> >
> > On Sat, May 7, 2011 at 2:28 PM, Xiaobo Gu <guxiaobo1982@gmail.com>
> wrote:
> > > On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <ted.dunning@gmail.com>
> > wrote:
> > >> Use
> > >>
> > >> mvn -DskipTests package
> > > But the above command only creates  jar files in seperated target
> > > directory, does not assamble them in a releaseable layout, I write the
> > > following lines in a package.sh file, but found several directories
> > > are not contained in trunk
> > >
> > > [gpadmin@lixsvr1 trunk]$ more package.sh
> > > #!/bin/bash
> > >
> > > rm -rf package/*
> > >
> > > cp -R bin package/
> > > cp -R docs package/
> > > cp -R conf package/
> > > cp -R examples package/
> > > cp -R lib package/
> > >
> > > cp core/target/*.jar package/
> > > cp examples/target/*.jar package/
> > > cp math/target/*.jar package/
> > > cp taste-web/target/*.war package/
> > > cp utils/target/*.jar package/
> > >
> > > [gpadmin@lixsvr1 trunk]$
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message