-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anders Hammar wrote:
> Wrong goal. Use single instead!
> Clearly stated in the docs...:-)
>
Thx Anders
Sometimes the simple solutions are the hardest to find :D
I was looking more into the release- and deploy-plugin to find out how
to get these to u
Wrong goal. Use single instead!
Clearly stated in the docs...:-)
/Anders
On Thu, Feb 11, 2010 at 14:46, Bastian Spanneberg <
bastian.spanneb...@linkwerk.com> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everybody
>
> We use Hudson and the maven-release-plugin to do our release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody
We use Hudson and the maven-release-plugin to do our release builds. Now
I have a project which contains an assembly that puts together all
needed components and then packages them into a .tar.gz package with the
desired directory structu
Hi all,
I'm looking to setup a method for auto-deploying some project artifacts
which have been packaged using the assembly plugin so they can be
downloaded through the site.
Right now i'm generating a tarball of an artifact and want to have it
copied to a web server directory so i can link
1. I don't see any reason why your technique should be considered bad. In
fact, we have an open issue in MASSEMBLY (assembly plugin jira) to add
installer-creators to the underlying archiver implementation (not sure
that's right architecture-wise, but the issue is there nonetheless).
2. I think y
I am using "mvn assembly:assembly deploy" command to upload my
distribution to the repository.
After that, to deploy it on the target machine, I use a simple Perl
script that downloads the assembly using http and then unpacks it.
Seems that this is pretty convenient thing, and my distributions are
