On 22 June 2013 20:39, Simone Tripodi <simonetrip...@apache.org> wrote: > There is an existing plugin[1] that supports checksums generation > applying a wider range of digest algorithm, it could help on inspiring > the ASF one.
Thanks. The one I wrote is equivalent to that plugins goals file/files, except mine has slightly simpler file config syntax; and does not yet support algorithms other than MD5 and SHA1. I don't see the point of creating hashes for dependencies; not entirely sure there's a need to do attached files either, given that this is currently done automatically during the deploy phase. However of course it could be added. > my 0.02 EU ;) > > [1] > http://nicoulaj.github.io/checksum-maven-plugin/examples/using-custom-checksum-algorithms.html > > http://people.apache.org/~simonetripodi/ > http://twitter.com/simonetripodi > > > On Sat, Jun 22, 2013 at 4:15 PM, Olivier Lamy <ol...@apache.org> wrote: >> what about moving this to maven plugins ? >> I'm pretty sure this could help some ASF projects. >> NOTE: the Maven sandbox path is open for all committers. >> And btw probably won't be hard to promote it and add sebb in maven >> committers. >> >> My 0.02 AUD >> >> 2013/6/22 Phil Steitz <phil.ste...@gmail.com>: >>> -0 >>> >>> I don't think this sort of things belongs in Commons proper as a >>> component. What we advertise, release and support from commons >>> proper are general purpose libraries that developers can use in >>> their own applications. This is what Commons was created for. >>> While the staging plugin looks like a useful thing for internal >>> commons use, I don't see it as a general purpose component. I see >>> it like the download plugin or commons parent. Perhaps what we >>> should do is formalize our policy to allow release of internal tools >>> so they can be grabbed from maven repos without actually promoting >>> them on the main commons web page or committing to support them for >>> external use. >>> >>> Phil >>> >>> On 6/21/13 7:06 AM, sebb wrote: >>>> [I'm not sure a vote for this is really needed, but] >>>> >>>> I'd like to move the staging plugin from the sandbox to commons >>>> proper, so it can be released for use by Commons. >>>> >>>> The component name is currently >>>> >>>> commons-staging-plugin >>>> >>>> I propose to keep the same name unless there are objections. >>>> >>>> The vote will close no sooner than 72 hours from now. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >> >> >> >> -- >> Olivier Lamy >> Ecetera: http://ecetera.com.au >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
