[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Metadata Stamp

There are probably too many open questions to make this a reality for 3.5, but thanks for discussing it.

I was thinking that many people would simply use one of the many publisher applications / ant tasks to generate their repositories, and if / when problems are reported, users are more likely to indicate which version of Eclipse they were using when they saw the problem, not which version of Eclipse they used to generate the metadata.

In practical terms, this happened last night.  Lucky for me it was in ECF and Scott is both on my skype list and in the same timezone as me, so we sorted it out rather quickly.  However, for random repositories on the web it might be harder to distinguish between a regression and someone that was using an old version of the tool.


On Wed, May 20, 2009 at 6:14 AM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:

The publisher itself isn't the one writing the file - it is agnostic of particular repository implementations. One possibility is that the publisher can add a property to the repository with some kind of publisher version stamp. It wouldn't be part of the metadata format, but it could be used as a debugging tool. However, I suspect it will be misleading. The repository could be initially created by the publisher, but then manipulated by other tools later on. There is rarely a single "author" for a given repository.

Sent by: p2-dev-bounces@xxxxxxxxxxx

05/20/2009 12:17 AM
Please respond to

P2 developer discussions <p2-dev@xxxxxxxxxxx>

P2 developer discussions <p2-dev@xxxxxxxxxxx>
[p2-dev] Metadata Stamp

Has anyone looked at what would be involved with stamping the metadata with the version of the publisher used to write it?  This would help when debugging publisher problems as we could easily see what version (including qualifier) of the publisher was being used. I actually think is important enough to consider for 3.5. I know we are stamping the metadata with a version,  but that is often not enough.


R. Ian Bull | EclipseSource Victoria | +1 250 477 7484

p2-dev mailing list

R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource