Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 398093 - Investigate removal of javax.xml.stream
Summary: Investigate removal of javax.xml.stream
Status: RESOLVED DUPLICATE of bug 383907
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-14 10:41 EST by Krzysztof Daniel CLA
Modified: 2013-01-18 06:35 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Krzysztof Daniel CLA 2013-01-14 10:41:21 EST
It looks like it is a part of jvm.
Comment 1 Steffen Pingel CLA 2013-01-14 11:59:24 EST
Shawn, I think we ran into problems with different versions of the bundle since we required a newer one than what was available in 1.5. Do you remember?
Comment 2 Shawn Minto CLA 2013-01-17 18:04:00 EST
The problem is that 1.5 does not have the packages (added in 1.6) and p2 does not provision the bundle properly.  See the following bug for more details.

341432: javax.xml.stream bundle is not provisioned when running java 1.5 with a package dependency
https://bugs.eclipse.org/bugs/show_bug.cgi?id=341432
Comment 3 Alexander Kurtakov CLA 2013-01-17 18:30:21 EST
(In reply to comment #2)
> The problem is that 1.5 does not have the packages (added in 1.6) and p2
> does not provision the bundle properly.  See the following bug for more
> details.
> 
> 341432: javax.xml.stream bundle is not provisioned when running java 1.5
> with a package dependency
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=341432

If 1.6 becomes the BREE this would no longer be a problem and there was a bug about that IIRC
Comment 4 Steffen Pingel CLA 2013-01-18 06:35:20 EST
Thanks very much! Let's track all of these removals on bug 383907 then.

*** This bug has been marked as a duplicate of bug 383907 ***