[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] making p2 metadata serializable
We talked about this last year, and the problem with serialization is the constraints placed on the format with respect to API. Once we declare the p2 metadata serializable, it would seem that you could read / write the data without worry. However, if a new field is added to the metadata, this assumption will break.
FWIW, a while ago I experimented with my own class structure that mirrored the metadata (for each class associated with the p2 metadata, there is a corresponding interface -- so this isn't too hard). I maked these as serializable and used this format. While it was better / faster / smaller than the compressed XML, the results weren't that impressive.
On Fri, Jan 21, 2011 at 8:57 PM, Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>
Tycho calculates and maintains build target platform for each project
individually. For larger builds, with tens or even hundreds of projects,
target platform resolution becomes quite time consuming so I am looking
for ways to optimise this. One optimisation I am considering is caching
resolved target platform instances between re-builds of the same project
and I was hoping to use serialization as an easy way to implement this.
p2 metadata is part of target platform state Tycho needs to maintain and
unfortunately p2 metadata is not serializable.
So as the subject says, is there a chance p2 metadata will become
serializable in 3.7 or I should look for alternative solutions?
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484http://eclipsesource.com