Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] MD5 hash is not as expected.

On Wed, Apr 11, 2012 at 5:29 PM, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
> I delete the MD5 entry from the artifacts.jar since P2 really throws wobblies if this is invalid. By deleting it from the artifacts.jar before publishing it to a repository it generally fixes the problem.
> This often happens when you are post-processing the JAR (e.g. signing it, Pack200 etc.) but after the P2 metadata step has completed. I have written a small XSLT to strip out the md5 from the XML (though you can use a command line tool like 'sed' if you haven't reflowed the content) as a specific post-processing step.

My internal bundle was created using
org.apache.felix:maven-bundle-plugin and is deployed in a standard M2
I dont have any P2 update site etc for this yet.

I'm using Nexus OSGi Experimental Features - P2 Repository Plugin
to expose the M2 repository as a P2 one.

I have two internally created bundles.
One works, the other fails with MD5 errors.
The MD5 is correct in the Nexus repository.

Ok, dumb questions following.

I dont think I have an artifacts.jar.

I'm trying to work out if Nexus or Tycho is doing something wrong (or
perhaps my bundle is wrong).
But since the download jar is deleted on failure I can't tell yet.

Back to hacking through code.

Back to the top