Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347667

Summary:	use eclipse-maven-signing-plugin results in "No location for packed"
Product:	[Technology] Dash	Reporter:	Igor Fedorenko <igor>
Component:	Maven	Assignee:	Project Dash Incoming bugs <dash-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	hmalphettes, pascal
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Igor Fedorenko

2011-05-30 11:35:25 EDT

Using eclipse-maven-signing-plugin to sign and do pack200 for m2e results in indigo aggregator build failure with messages like below for all m2e bundles

"org.eclipse.core.runtime.CoreException: Unable to mirror artifact osgi.bundle,org.eclipse.m2e.lifecyclemapping.defaults,0.13.0.201105252313 from repository http://download.eclipse.org/technology/m2e/updates/M: No location for packed: osgi.bundle,org.eclipse.m2e.lifecyclemapping.defaults,0.13.0.201105252313."

After a quick look it appears that eclipse-maven-signing-plugin:fixCheckSums does not add artifact repository mapping rules for packed artifacts and this seems to confuse b3 aggregaror build (installation from p2 gui still works).

Comment 1 Hugues Malphettes

2011-06-01 22:24:11 EDT

Duplicate of bug 347591.

> installation from p2 gui still works
p2 director just does not find the packed artifacts.
So it uses the unpacked ones and the issue remains hidden.

A fast way to reproduce the error reported by the aggregator is to run p2mirror-artifacts against the repository.

*** This bug has been marked as a duplicate of bug 347591 ***