Re: [cross-project-issues-dev] Maven signing plugin and unexpected MD5

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

it works in the limited sets of projects we have run it against...but
it possible there are scenarios like this that need addressed still.

You ran the fix checksum mojo after all the signing and packing?

anyway, if it's a problem please open an issue in bugzilla and detail
the problem and we'll try and get it spruced up for use case.
pointing to the build output and mojo configuration is important.

cheers,
Jesse

On Monday, May 23, 2011, Vincent Zurczak <vincent.zurczak@xxxxxxxxxxxxxx> wrote:
>
>
>
>
>
>
>     Hi,
>
>     I use the Maven signing plugin for Eclipse [0] to pack and sign SCA
>     Toools.
>     Everything looks fine, except that when I try to install it in
>     Indigo M6, the installation fails due to wrong MD5.
>     It appears the MD5 values in artifacts.xml are not updated in the
>     build process. They are exactly the same in the original site and in
>     the checksum directory.
>
>     Besides, I noticed the final artifacts.xml file declares new
>     artifacts at the end, some of them with a wrong version.
>     It results in warnings at the installation.
>
>     Am I the only one to have these problems?
>
>     Regards,
>
>                      Vincent.
>
>
>     [ 0 ] : https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336
>
>     --
>       Vincent Zurczak
>
>       R&D Engineer
>       Petals Link <http://www.petalslink.com> - SOA
>       open-source company
>       http://vzurczak.wordpress.com
>
>       +33 (0) 4 76 96 15 16
>
>
>

-- 
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx