Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312366 - [repository] Review behaviour of 3.6 repo when loading an IU of generation > 2
Summary: [repository] Review behaviour of 3.6 repo when loading an IU of generation > 2
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-10 22:58 EDT by Pascal Rapicault CLA
Modified: 2019-10-13 17:57 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2010-05-10 22:58:31 EDT
We should prepare for the eventuality of having to create yet another serialization format for IU and make sure that the repo reader handle the appearance of generation attribute superior to 2 in a graceful way.
Comment 1 Thomas Hallgren CLA 2010-05-11 03:26:47 EDT
I'd suggest that we do this with Xtext. It could help us to create a very compact and yet very readable serialization format. We could then also use this format to actually author individual IU's (with syntax coloring, code completion, and all other bells and whistles that comes in the same bag).

p2 should probably have it's own serializer/parser for the syntax that we create so that we don't introduce more dependencies to the actual runtime.
Comment 2 Thomas Watson CLA 2011-06-08 11:28:24 EDT
Move all 3.8 bugs to Juno.
Comment 3 Ian Bull CLA 2012-06-29 12:30:11 EDT
Any point in keeping this bug open?
Comment 4 Eclipse Genie CLA 2019-10-13 17:57:32 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.