| Summary: | Include Java EE 6 XML Schema files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Kaloyan Raev <kaloyan> | ||||
| Component: | wst.xml | Assignee: | Nitin Dahyabhai <thatnitind> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Nitin Dahyabhai <thatnitind> | ||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | ccc, ludo, raccah, valentinbaciu | ||||
| Version: | 3.1 | Keywords: | plan | ||||
| Target Milestone: | 3.2 M5 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | JavaEE6 | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 252615, 260839, 299666 | ||||||
| Attachments: |
|
||||||
|
Description
Kaloyan Raev
Decommitting Java EE 6 support for WTP 3.1 For now, we've added the EE 6 schemas in the GlassFish v3 Java EE 6 plugin, but feel free to take them from a v3 runtime and register them (this will complete the EE 6 facet currently done) We do need to go through the Eclipse CQ process on these to make sure there are no legal issues for WTP to ship these. (And frankly, I am concerned that there might be, due to the GPL2 license all over the xsds.) Once the CQ process is complete, we will put these into the XML catalog. All the EE 6 schemas should be dual license CDDL or GPLv2. If this is not the case, let me know... I think the CDDL choice for you is the way to go. Nitin, https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2982 is now at checkintocvs , so we are clear to add these xsds into org.eclipse.jst.standard.schemas. Created attachment 155391 [details]
The approved xsds and an updated plugin.xml
I believe I added these to the XML Catalog correctly.
I guess the JPA (orm 2, persistence 2...)and JSF 2.0 (faceconfig 2,... ) related new schemas will be posted on other modules that would be always available and started when this plugin is used? What about beans_1.0.xsd for CDI/Weld support? In reply to comment #7 - This bug is to cover the xsds required by the Java EE Tooling (and EJB Tooling) in WTP. The JPA artifacts should be handled by a committer on the Dali team, and the JSF artifacts should be handled by a committer on the Java Server Faces team. (I am not sure who should handle the CDI/Weld one... but whatever team handles that support/tooling should do the request.) Now, having said that, there is no reason why bugs cannot be opened against Dali and Java Server Faces to ask them to get those xsds registered in the XML Catalog. Released. *** Bug 260785 has been marked as a duplicate of this bug. *** |