You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mahout.apache.org by Xiaobo Gu <gu...@gmail.com> on 2011/05/06 17:30:32 UTC
Re: Which maven command to use to put all the binaries into the
distribution layout?
mvn -Prelease prompt me to enter a password for :GPG Passphrase:
And I can't provide one.
How can I build and package the release zip file without running the unit tests?
Another question, why the mvn download a lot of files from the
Internet while building?
Regards,
On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <bi...@gmail.com> wrote:
> Um, mvn -Prelease?
>
>
> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
>> It should be "mvn release"
>>
>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>>
>>> I mean to build to released package such as mahout-distribution-0.4.zip
>>>
>>
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Benson Margulies <bi...@gmail.com>.
I imagine it's -Prelease,mahout_release that is missing from the
conversation. The build economizes the expensive process of building
full release packages unless you turn on the profile.
On Sat, May 7, 2011 at 9:43 AM, Xiaobo Gu <gu...@gmail.com> wrote:
> On Sat, May 7, 2011 at 9:41 PM, Sean Owen <sr...@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.
>
> [gpadmin@lixsvr1 trunk]$ ./package.sh
> cp: cannot stat `docs': No such file or directory
> cp: cannot stat `conf': No such file or directory
> cp: cannot stat `lib': No such file or directory
>
>>
>> On Sat, May 7, 2011 at 2:28 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>>> On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <te...@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]$
>>
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Xiaobo Gu <gu...@gmail.com>.
On Sat, May 7, 2011 at 9:41 PM, Sean Owen <sr...@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.
[gpadmin@lixsvr1 trunk]$ ./package.sh
cp: cannot stat `docs': No such file or directory
cp: cannot stat `conf': No such file or directory
cp: cannot stat `lib': No such file or directory
>
> On Sat, May 7, 2011 at 2:28 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>> On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <te...@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]$
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Jake Mannix <ja...@gmail.com>.
Nope, that's spurious output, don't worry about it.
-jake
On Sat, May 7, 2011 at 7:56 PM, XiaoboGu <gu...@gmail.com> wrote:
> The command does what I want, but during building, the output contains
> something like this:
>
> [INFO] --- maven-javadoc-plugin:2.7:jar (attach-javadocs) @
> mahout-taste-webapp ---
> [ERROR] Error fetching link:
> /home/gpadmin/mahout/src-trunk/trunk/buildtools/target/apidocs/package-list.
> Ignored it.
> [ERROR] Error fetching link:
> /home/gpadmin/mahout/src-trunk/trunk/eclipse/target/apidocs/package-list.
> Ignored it.
>
>
> Does it matter?
>
> Xiaobo Gu
>
>
> > -----Original Message-----
> > From: Ted Dunning [mailto:ted.dunning@gmail.com]
> > Sent: Sunday, May 08, 2011 6:19 AM
> > To: user@mahout.apache.org
> > Subject: Re: Which maven command to use to put all the binaries into the
> distribution layout?
> >
> > This simpler form works as well:
> >
> > mvn -DskipTests -Prelease package
> >
> >
> > On Sat, May 7, 2011 at 2:52 PM, Jake Mannix <ja...@gmail.com>
> wrote:
> >
> > > Wow, now it's working fine, not complaining.
> > >
> > > Xiaobo: this is the way to build your distribution!
> > >
> > > mvn -DskipTests -Prelease,mahout_release package
> > >
> > > and look in distribution/target for your zip/bz2/etc packages.
> > >
> > > -jake
> > >
> > > On Sat, May 7, 2011 at 2:45 PM, Jake Mannix <ja...@gmail.com>
> wrote:
> > >
> > > >
> > > >
> > > > On Sat, May 7, 2011 at 2:40 PM, Ted Dunning <te...@gmail.com>
> > > wrote:
> > > >
> > > >> 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
> > > >>
> > > >
> > > > See, when I tried this, I got complaints about gpg, but then I
> commented
> > > > out
> > > > the lines in the top level pom which had the "maven-gpg-plugin", and
> it
> > > > built fine into distribution/target just fine.
> > > >
> > > > -jake
> > > >
> > >
>
>
RE: Which maven command to use to put all the binaries into the distribution layout?
Posted by XiaoboGu <gu...@gmail.com>.
The command does what I want, but during building, the output contains something like this:
[INFO] --- maven-javadoc-plugin:2.7:jar (attach-javadocs) @ mahout-taste-webapp ---
[ERROR] Error fetching link: /home/gpadmin/mahout/src-trunk/trunk/buildtools/target/apidocs/package-list. Ignored it.
[ERROR] Error fetching link: /home/gpadmin/mahout/src-trunk/trunk/eclipse/target/apidocs/package-list. Ignored it.
Does it matter?
Xiaobo Gu
> -----Original Message-----
> From: Ted Dunning [mailto:ted.dunning@gmail.com]
> Sent: Sunday, May 08, 2011 6:19 AM
> To: user@mahout.apache.org
> Subject: Re: Which maven command to use to put all the binaries into the distribution layout?
>
> This simpler form works as well:
>
> mvn -DskipTests -Prelease package
>
>
> On Sat, May 7, 2011 at 2:52 PM, Jake Mannix <ja...@gmail.com> wrote:
>
> > Wow, now it's working fine, not complaining.
> >
> > Xiaobo: this is the way to build your distribution!
> >
> > mvn -DskipTests -Prelease,mahout_release package
> >
> > and look in distribution/target for your zip/bz2/etc packages.
> >
> > -jake
> >
> > On Sat, May 7, 2011 at 2:45 PM, Jake Mannix <ja...@gmail.com> wrote:
> >
> > >
> > >
> > > On Sat, May 7, 2011 at 2:40 PM, Ted Dunning <te...@gmail.com>
> > wrote:
> > >
> > >> 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
> > >>
> > >
> > > See, when I tried this, I got complaints about gpg, but then I commented
> > > out
> > > the lines in the top level pom which had the "maven-gpg-plugin", and it
> > > built fine into distribution/target just fine.
> > >
> > > -jake
> > >
> >
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Ted Dunning <te...@gmail.com>.
This simpler form works as well:
mvn -DskipTests -Prelease package
On Sat, May 7, 2011 at 2:52 PM, Jake Mannix <ja...@gmail.com> wrote:
> Wow, now it's working fine, not complaining.
>
> Xiaobo: this is the way to build your distribution!
>
> mvn -DskipTests -Prelease,mahout_release package
>
> and look in distribution/target for your zip/bz2/etc packages.
>
> -jake
>
> On Sat, May 7, 2011 at 2:45 PM, Jake Mannix <ja...@gmail.com> wrote:
>
> >
> >
> > On Sat, May 7, 2011 at 2:40 PM, Ted Dunning <te...@gmail.com>
> wrote:
> >
> >> 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
> >>
> >
> > See, when I tried this, I got complaints about gpg, but then I commented
> > out
> > the lines in the top level pom which had the "maven-gpg-plugin", and it
> > built fine into distribution/target just fine.
> >
> > -jake
> >
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Jake Mannix <ja...@gmail.com>.
Wow, now it's working fine, not complaining.
Xiaobo: this is the way to build your distribution!
mvn -DskipTests -Prelease,mahout_release package
and look in distribution/target for your zip/bz2/etc packages.
-jake
On Sat, May 7, 2011 at 2:45 PM, Jake Mannix <ja...@gmail.com> wrote:
>
>
> On Sat, May 7, 2011 at 2:40 PM, Ted Dunning <te...@gmail.com> wrote:
>
>> 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
>>
>
> See, when I tried this, I got complaints about gpg, but then I commented
> out
> the lines in the top level pom which had the "maven-gpg-plugin", and it
> built fine into distribution/target just fine.
>
> -jake
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Jake Mannix <ja...@gmail.com>.
On Sat, May 7, 2011 at 2:40 PM, Ted Dunning <te...@gmail.com> wrote:
> 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
>
See, when I tried this, I got complaints about gpg, but then I commented out
the lines in the top level pom which had the "maven-gpg-plugin", and it
built fine into distribution/target just fine.
-jake
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Ted Dunning <te...@gmail.com>.
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 <ja...@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 <sr...@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 <gu...@gmail.com>
> wrote:
> > > On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <te...@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]$
> >
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Jake Mannix <ja...@gmail.com>.
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 <sr...@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 <gu...@gmail.com> wrote:
> > On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <te...@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]$
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Sean Owen <sr...@gmail.com>.
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 <gu...@gmail.com> wrote:
> On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <te...@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]$
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Xiaobo Gu <gu...@gmail.com>.
On Sat, May 7, 2011 at 3:30 PM, Ted Dunning <te...@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]$
> On Fri, May 6, 2011 at 8:50 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>
>> On Fri, May 6, 2011 at 11:34 PM, Sean Owen <sr...@gmail.com> wrote:
>> > I think you'd have to set up release keys and all that to make the
>> package.
>> > Does "mvn release:prepare" (without -Prelease) do what you want or am
>> > I crazy? That's ultimately what makes the artifacts. Here's our
>> > process:
>> https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
>> >
>> > What are you trying to do though, there may be a much easier way. I
>> > doubt you want to run the release.
>>
>> I just want to build a daily build of the latest source code of trunk
>> on my desktop, and deploy it on our big servers, don't want to do the
>> build and package operation on all servers.
>> BTW, our servers can't connect to the Internet.
>>
>> >
>> > Maven always has to download plugins and dependencies the first time.
>> > It's normal.
>> >
>> > Sean
>> >
>> > On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com>
>> wrote:
>> >> mvn -Prelease prompt me to enter a password for :GPG Passphrase:
>> >> And I can't provide one.
>> >>
>> >> How can I build and package the release zip file without running the
>> unit tests?
>> >>
>> >>
>> >> Another question, why the mvn download a lot of files from the
>> >> Internet while building?
>> >>
>> >> Regards,
>> >>
>> >>
>> >>
>> >> On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <
>> bimargulies@gmail.com> wrote:
>> >>> Um, mvn -Prelease?
>> >>>
>> >>>
>> >>> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
>> >>>> It should be "mvn release"
>> >>>>
>> >>>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com>
>> wrote:
>> >>>>
>> >>>>> I mean to build to released package such as
>> mahout-distribution-0.4.zip
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Ted Dunning <te...@gmail.com>.
Use
mvn -DskipTests package
On Fri, May 6, 2011 at 8:50 PM, Xiaobo Gu <gu...@gmail.com> wrote:
> On Fri, May 6, 2011 at 11:34 PM, Sean Owen <sr...@gmail.com> wrote:
> > I think you'd have to set up release keys and all that to make the
> package.
> > Does "mvn release:prepare" (without -Prelease) do what you want or am
> > I crazy? That's ultimately what makes the artifacts. Here's our
> > process:
> https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
> >
> > What are you trying to do though, there may be a much easier way. I
> > doubt you want to run the release.
>
> I just want to build a daily build of the latest source code of trunk
> on my desktop, and deploy it on our big servers, don't want to do the
> build and package operation on all servers.
> BTW, our servers can't connect to the Internet.
>
> >
> > Maven always has to download plugins and dependencies the first time.
> > It's normal.
> >
> > Sean
> >
> > On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com>
> wrote:
> >> mvn -Prelease prompt me to enter a password for :GPG Passphrase:
> >> And I can't provide one.
> >>
> >> How can I build and package the release zip file without running the
> unit tests?
> >>
> >>
> >> Another question, why the mvn download a lot of files from the
> >> Internet while building?
> >>
> >> Regards,
> >>
> >>
> >>
> >> On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <
> bimargulies@gmail.com> wrote:
> >>> Um, mvn -Prelease?
> >>>
> >>>
> >>> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
> >>>> It should be "mvn release"
> >>>>
> >>>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com>
> wrote:
> >>>>
> >>>>> I mean to build to released package such as
> mahout-distribution-0.4.zip
> >>>>>
> >>>>
> >>>
> >>
> >
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Xiaobo Gu <gu...@gmail.com>.
On Fri, May 6, 2011 at 11:34 PM, Sean Owen <sr...@gmail.com> wrote:
> I think you'd have to set up release keys and all that to make the package.
> Does "mvn release:prepare" (without -Prelease) do what you want or am
> I crazy? That's ultimately what makes the artifacts. Here's our
> process: https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
>
> What are you trying to do though, there may be a much easier way. I
> doubt you want to run the release.
I just want to build a daily build of the latest source code of trunk
on my desktop, and deploy it on our big servers, don't want to do the
build and package operation on all servers.
BTW, our servers can't connect to the Internet.
>
> Maven always has to download plugins and dependencies the first time.
> It's normal.
>
> Sean
>
> On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>> mvn -Prelease prompt me to enter a password for :GPG Passphrase:
>> And I can't provide one.
>>
>> How can I build and package the release zip file without running the unit tests?
>>
>>
>> Another question, why the mvn download a lot of files from the
>> Internet while building?
>>
>> Regards,
>>
>>
>>
>> On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <bi...@gmail.com> wrote:
>>> Um, mvn -Prelease?
>>>
>>>
>>> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
>>>> It should be "mvn release"
>>>>
>>>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>>>>
>>>>> I mean to build to released package such as mahout-distribution-0.4.zip
>>>>>
>>>>
>>>
>>
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Ted Dunning <te...@gmail.com>.
Which is glued to the package life cycle in Mahout.
On Fri, May 6, 2011 at 9:42 AM, Patrick Angeles <pa...@cloudera.com>wrote:
> You probably want the maven assembly plugin.
>
> On Fri, May 6, 2011 at 12:07 PM, Ted Dunning <te...@gmail.com>
> wrote:
>
> > Isn't there a mvn package target that is better for this?
> >
> > On Fri, May 6, 2011 at 8:34 AM, Sean Owen <sr...@gmail.com> wrote:
> >
> > > I think you'd have to set up release keys and all that to make the
> > package.
> > > Does "mvn release:prepare" (without -Prelease) do what you want or am
> > > I crazy? That's ultimately what makes the artifacts. Here's our
> > > process:
> > https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
> > >
> > > What are you trying to do though, there may be a much easier way. I
> > > doubt you want to run the release.
> > >
> > > Maven always has to download plugins and dependencies the first time.
> > > It's normal.
> > >
> > > Sean
> > >
> > > On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com>
> > wrote:
> > > > mvn -Prelease prompt me to enter a password for :GPG Passphrase:
> > > > And I can't provide one.
> > > >
> > > > How can I build and package the release zip file without running the
> > unit
> > > tests?
> > > >
> > > >
> > > > Another question, why the mvn download a lot of files from the
> > > > Internet while building?
> > > >
> > > > Regards,
> > > >
> > > >
> > > >
> > > > On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <
> > bimargulies@gmail.com>
> > > wrote:
> > > >> Um, mvn -Prelease?
> > > >>
> > > >>
> > > >> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com>
> wrote:
> > > >>> It should be "mvn release"
> > > >>>
> > > >>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <guxiaobo1982@gmail.com
> >
> > > wrote:
> > > >>>
> > > >>>> I mean to build to released package such as
> > > mahout-distribution-0.4.zip
> > > >>>>
> > > >>>
> > > >>
> > > >
> > >
> >
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Patrick Angeles <pa...@cloudera.com>.
You probably want the maven assembly plugin.
On Fri, May 6, 2011 at 12:07 PM, Ted Dunning <te...@gmail.com> wrote:
> Isn't there a mvn package target that is better for this?
>
> On Fri, May 6, 2011 at 8:34 AM, Sean Owen <sr...@gmail.com> wrote:
>
> > I think you'd have to set up release keys and all that to make the
> package.
> > Does "mvn release:prepare" (without -Prelease) do what you want or am
> > I crazy? That's ultimately what makes the artifacts. Here's our
> > process:
> https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
> >
> > What are you trying to do though, there may be a much easier way. I
> > doubt you want to run the release.
> >
> > Maven always has to download plugins and dependencies the first time.
> > It's normal.
> >
> > Sean
> >
> > On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com>
> wrote:
> > > mvn -Prelease prompt me to enter a password for :GPG Passphrase:
> > > And I can't provide one.
> > >
> > > How can I build and package the release zip file without running the
> unit
> > tests?
> > >
> > >
> > > Another question, why the mvn download a lot of files from the
> > > Internet while building?
> > >
> > > Regards,
> > >
> > >
> > >
> > > On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <
> bimargulies@gmail.com>
> > wrote:
> > >> Um, mvn -Prelease?
> > >>
> > >>
> > >> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
> > >>> It should be "mvn release"
> > >>>
> > >>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com>
> > wrote:
> > >>>
> > >>>> I mean to build to released package such as
> > mahout-distribution-0.4.zip
> > >>>>
> > >>>
> > >>
> > >
> >
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Ted Dunning <te...@gmail.com>.
Isn't there a mvn package target that is better for this?
On Fri, May 6, 2011 at 8:34 AM, Sean Owen <sr...@gmail.com> wrote:
> I think you'd have to set up release keys and all that to make the package.
> Does "mvn release:prepare" (without -Prelease) do what you want or am
> I crazy? That's ultimately what makes the artifacts. Here's our
> process: https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
>
> What are you trying to do though, there may be a much easier way. I
> doubt you want to run the release.
>
> Maven always has to download plugins and dependencies the first time.
> It's normal.
>
> Sean
>
> On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com> wrote:
> > mvn -Prelease prompt me to enter a password for :GPG Passphrase:
> > And I can't provide one.
> >
> > How can I build and package the release zip file without running the unit
> tests?
> >
> >
> > Another question, why the mvn download a lot of files from the
> > Internet while building?
> >
> > Regards,
> >
> >
> >
> > On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <bi...@gmail.com>
> wrote:
> >> Um, mvn -Prelease?
> >>
> >>
> >> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
> >>> It should be "mvn release"
> >>>
> >>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com>
> wrote:
> >>>
> >>>> I mean to build to released package such as
> mahout-distribution-0.4.zip
> >>>>
> >>>
> >>
> >
>
Re: Which maven command to use to put all the binaries into the
distribution layout?
Posted by Sean Owen <sr...@gmail.com>.
I think you'd have to set up release keys and all that to make the package.
Does "mvn release:prepare" (without -Prelease) do what you want or am
I crazy? That's ultimately what makes the artifacts. Here's our
process: https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Release
What are you trying to do though, there may be a much easier way. I
doubt you want to run the release.
Maven always has to download plugins and dependencies the first time.
It's normal.
Sean
On Fri, May 6, 2011 at 4:30 PM, Xiaobo Gu <gu...@gmail.com> wrote:
> mvn -Prelease prompt me to enter a password for :GPG Passphrase:
> And I can't provide one.
>
> How can I build and package the release zip file without running the unit tests?
>
>
> Another question, why the mvn download a lot of files from the
> Internet while building?
>
> Regards,
>
>
>
> On Mon, Apr 11, 2011 at 1:31 AM, Benson Margulies <bi...@gmail.com> wrote:
>> Um, mvn -Prelease?
>>
>>
>> On Sun, Apr 10, 2011 at 12:34 PM, Sean Owen <sr...@gmail.com> wrote:
>>> It should be "mvn release"
>>>
>>> On Sun, Apr 10, 2011 at 4:52 PM, Xiaobo Gu <gu...@gmail.com> wrote:
>>>
>>>> I mean to build to released package such as mahout-distribution-0.4.zip
>>>>
>>>
>>
>