Eclipse Community Forums: P2 » Impact of replacing artifacts from an update site

Home » Eclipse Projects » P2 » Impact of replacing artifacts from an update site

Impact of replacing artifacts from an update site [message #1755249]

Wed, 01 March 2017 10:57

Eclipse User

Hi,

I am currently investigating code signing for my Eclipse plug-ins ( https://sling.apache.org/documentation/development/ide-tooling.html ). I build the plug-ins using Tycho.

The solution that is currently available to me does not have a Maven plug-in available, so I would either need to write on or use a Web UI.

If I decide to use the Web UI, then the artifacts (jars/features) will be changed after the update site is packaged. I see that there are various propeties of artifacts ( download.size, artifact.size ) that are referenced in artifacts.jar that will be incorrect after the signing.

Testing on a local update site did not result in any problems, but I can't be sure this will always be the case.

Is it safe to replace the artifacts from an existing update site with ones with a slightly larger size?

Thanks,

Robert

Re: Impact of replacing artifacts from an update site [message #1755889 is a reply to message #1755249]

Wed, 08 March 2017 20:49

Eclipse User

Typically you'd re-publish your newly signed artifacts into a new repository with the features and bundles publisher.

I don't think replacement as you're doing is likely to be safe: in addition to the size, the artifacts.xml/jar may also include an file hash (MD5) too.

Brian.

Re: Impact of replacing artifacts from an update site [message #1758313 is a reply to message #1755889]

Mon, 27 March 2017 11:02

Eclipse User

Right. I'll have to take the long way then.

Thanks

Previous Topic:	How to update with p2 directory without the logback error?
Next Topic:	How to update after merging two features?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 05 02:15:10 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter