Actually, the most helpful thing would be if someone from P2 could comment on this bugzilla, which was resolved as "WONT FIX"
https://bugs.eclipse.org/bugs/show_bug.cgi?id=305939
I'd appreciate it greatly.
---------------------------------------------
Marcus Kestler
Advisory Software Engineer
IBM Rational Capilano Group
---------------------------------------------
Thomas Hallgren ---03/16/2010 12:00:00 PM---Hi Marcus, I'm fairly certain that the p2 tooling isn't the culprit. The publisher will keep the ar
From: |
Thomas Hallgren <thomas@xxxxxxx> |
To: |
P2 developer discussions <p2-dev@xxxxxxxxxxx> |
Date: |
03/16/2010 12:00 PM |
Subject: |
Re: [p2-dev] Pack200 and Canonical Descriptor Issue |
Sent by: |
p2-dev-bounces@xxxxxxxxxxx |
Hi Marcus,
I'm fairly certain that the p2 tooling isn't the culprit. The publisher will keep the artifact.xml (or .jar) consistent with the actual content of the site. It sounds to me like the builder in this case just removes the canonical jars without updating the descriptor index. It relies on the p2 default "fallback to canonical" mechanism.
A well behaved builder will instead access the IArtifactRepository through it's api and remove the artifacts that way (I recently wrote the code for that in Buckminster so give me a ping if you're interested).
Regards,
Thomas Hallgren
On 03/16/2010 04:45 PM, Marcus R Kestler wrote:
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
|