commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: [all] How to prevent mvn deploy to skip certain artifacts
Date Wed, 03 Apr 2013 09:56:37 GMT
On 3 April 2013 10:49, Mladen Turk <> 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 won't be deployed.
> Seems exactly what I was looking for. Thanks!
> So for daemon I would set attach=false to bin, native-src and src
> assemblies
> meaning only win and .jar would be deployed. Nice.

Unfortunately that also detaches the archives from the hash generation
So you need to add code (e.g. antrun) to create the hashes.

line# approx: 1200

[taken from posting on Creadur/RAT list]

You may find it also drops the archives from the signing phase.


Although there is a disadvantage to the current process (the Nexus repo
needs to be tidied up before release), there is the advantage that the
Nexus repo can act as the staging repo for the archives as well. This may
not be suitable for all ASF projects, but in general it can work well.

> Regards
> --
> ^TM
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**<>
> For additional commands, e-mail:

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