Hi Brett!

FWIK MD5 creation actually takes place when you do a mvn deploy, but not on mvn 
install.

This assemblies are not ment to be treated as attached artifacts, so the 
assembly:single will not be bound to the package phase resp. the install phase 
will not be invoked.

The usecase I have in mind is the following:

First, we'll do the openwebbeans build with the maven-release-plugin. So SVN 
gets tagged, all modules are deployed to the maven-repo, etc.
Later we will additionally start building the distribution packages manually 
from this tag. The created zips and tar.gzs will be hosted on the incubator 
page for all people/projects who are interested and do _not_ use maven.

I thought about having a configuration like:
<createDigests>MD5, SHA1</createDigests>
and create a 
 MessageDigest.getInstance(digest); 
for each of them.

The main reason why I'd add it to the assembly plugin is because this plugin 
already knows about all the generated assemblies. 

Otoh, can you imagine any situation where you like to hash another file?

The more I think about it: it wouldn't be a problem to make a new plugin with 
an include/exclude list in codehaus.sandbox for this.

WDYT?

LieGrue,
strub

--- Brett Porter <[email protected]> schrieb am Sa, 10.1.2009:
> Von: Brett Porter <[email protected]>
> Betreff: Re: md5 for assemblies - how do you do it?
> An: "Maven Users List" <[email protected]>
> Datum: Samstag, 10. Januar 2009, 23:07
> When they are created or when they are installed? It should
> happen with the latter, it isn't usually the case for
> the former (And would suggest a separate plugin for that).
> 
> - Brett
> 
> On 11/01/2009, at 7:35 AM, Mark Struberg wrote:
> 
> > Hi!
> > 
> > I've configured the maven-assembly-plugin for a
> project to generate 3 tar.gz archives dist-sources,
> dist-binary and dist-all.
> > 
> > So it would be no problem to do a manual md5sum over
> those files, but I'm a lazy guy and like to have maven
> do this for me ;)
> > 
> > I've read through the plugin docu and jira, but it
> seems that the maven-assembly-plugin cannot generate MD5
> and/or SHA1 for the generated assemblies?
> > 
> > So how would you do it?
> > 
> > Or should I simply create a Jira and patch the plugin
> with using java.security.MessageDigest?





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to