Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347667 - use eclipse-maven-signing-plugin results in "No location for packed"
Summary: use eclipse-maven-signing-plugin results in "No location for packed"
Status: RESOLVED DUPLICATE of bug 347591
Alias: None
Product: Dash
Classification: Technology
Component: Maven (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Dash Incoming bugs CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-30 11:35 EDT by Igor Fedorenko CLA
Modified: 2011-06-01 22:24 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 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 CLA 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 ***