On Thu, Apr 4, 2013 at 6:25 AM, Mladen Turk mt...@apache.org wrote:
Why? It's a RM's job to sign the files at the time he proposes a vote.
That's the only time this stuff is needed.
The best would be to have some sort of 'dist' target that would prepare
the stuff for non-maven publishing.
On 4 April 2013 05:25, Mladen Turk mt...@apache.org wrote:
On 04/03/2013 08:29 PM, sebb wrote:
On 3 April 2013 11:19, Mladen Turk mt...@apache.org wrote:
Unfortunately that also detaches the archives from the hash generation
process.
So you need to add code (e.g. antrun) to create the
On 2013-04-04, Mladen Turk wrote:
So it seems the gpg-sign plugin in #28 uses gpg differently. And it
seems running gpg-agent is needed and sloves the issue. Just in case
someone else bumps into that.
Could you add this piece of knowledge to
Hi,
There's been a discussion about not deploying certain type of artifacts
to Maven repository (upon which I totally agree).
However how can this be done. Except from manually cleaning up open staging
repo of course.
It would be nice to have some sort of list which types of artifact gets
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the project
by setting to `false` the `attach`[1] property.
In that way, -(src|bin)\.(zip|tar\.gz) artifacts won't be deployed.
HTH!
-Simo
[1]
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#attach
On 04/03/2013 10:02 AM, Simone Tripodi wrote:
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the project
by setting to `false` the `attach`[1] property.
In that way, -(src|bin)\.(zip|tar\.gz) artifacts won't be deployed.
Seems exactly what I was looking for.
On 3 April 2013 10:49, Mladen Turk mt...@apache.org wrote:
On 04/03/2013 10:02 AM, Simone Tripodi wrote:
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the project
by setting to `false` the `attach`[1] property.
In that way, -(src|bin)\.(zip|tar\.gz) artifacts
On 04/03/2013 11:56 AM, sebb wrote:
On 3 April 2013 10:49, Mladen Turk mt...@apache.org wrote:
On 04/03/2013 10:02 AM, Simone Tripodi wrote:
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the project
by setting to `false` the `attach`[1] property.
In that way,
On 3 April 2013 11:19, Mladen Turk mt...@apache.org wrote:
On 04/03/2013 11:56 AM, sebb wrote:
On 3 April 2013 10:49, Mladen Turk mt...@apache.org wrote:
On 04/03/2013 10:02 AM, Simone Tripodi wrote:
Hi Mladen!
artifacts produced by the assembly-plugin can be detached from the
project
On 04/03/2013 08:29 PM, sebb wrote:
On 3 April 2013 11:19, Mladen Turk mt...@apache.org wrote:
Unfortunately that also detaches the archives from the hash generation
process.
So you need to add code (e.g. antrun) to create the hashes.
That's fine. I know how to use md5sum and gpg. No need
On 04/03/2013 08:29 PM, sebb wrote:
On 3 April 2013 11:19, Mladen Turk mt...@apache.org wrote:
Anyhow, gpg sign fails for commons-parent #28. #27 and earlier work.
First I've heard of that.
CP 28 has been used successfully elsewhere AFAIK.
It doesn't work in interactive mode. However
11 matches
Mail list logo
