Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341162 - Separate XML support
Summary: Separate XML support
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Konstantin Komissarchik CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2011-03-28 16:09 EDT by Konstantin Komissarchik CLA
Modified: 2021-11-19 09:21 EST (History)
1 user (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 Konstantin Komissarchik CLA 2011-03-28 16:09:07 EDT 
The support for XML binding in Sapphire Modeling Framework should be packaged into a separate "Sapphire XML Support" plugin and feature.
Comment 1 Konstantin Komissarchik CLA 2011-03-28 22:54:14 EDT 
Change implemented. 

The XML support is now located in a bundle and a feature with the following shared id:

org.eclipse.sapphire.modeling.xml

This will affect adopters and necessitate changes to Requite-Bundle declarations. Added content to the migration guide.

This change also required splitting org.eclipse.sapphire feature into separate features for modeling and ui frameworks. The new feature ids are these:

org.eclipse.sapphire.modeling
org.eclipse.sapphire.ui

The prior org.eclipse.sapphire feature has been eliminated. 

These changes will likely make it impossible to install 0.3 on top of a 0.2.x installation as an upgrade. A fresh install will be necessary.
Comment 2 Ram Venkataswamy CLA 2011-06-02 13:18:29 EDT 
verified with build 0.3.0.201105261624
Comment 3 Konstantin Komissarchik CLA 2011-06-03 12:17:54 EDT 
Closing.