Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTPNewsletter 20080407"
| (One intermediate revision by the same user not shown) | |||
| Line 13: | Line 13: | ||
*[http://wiki.eclipse.org/WTP_Functional_Test_R30_M6 FVT Results] | *[http://wiki.eclipse.org/WTP_Functional_Test_R30_M6 FVT Results] | ||
| + | |||
| + | *Please note that the "all in ones" will be available on 4/15 and Ganymede's M6 release date is 4/16. | ||
*[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&classification=WebTools&target_milestone=3.0+M6&target_milestone=2.0+M6&resolution=FIXED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&chfieldfrom=2008-03-28&chfieldto=2008-04-07&chfield=resolution&chfieldvalue=FIXED&format=table&action=wrap 3.0 Bugs fixed this week] | *[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&classification=WebTools&target_milestone=3.0+M6&target_milestone=2.0+M6&resolution=FIXED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&chfieldfrom=2008-03-28&chfieldto=2008-04-07&chfield=resolution&chfieldvalue=FIXED&format=table&action=wrap 3.0 Bugs fixed this week] | ||
Latest revision as of 00:51, 8 April 2008
Contents
WTP Weekly What's Cooking?
Headline News!
- WTP 3.0 M6 Milestone build declared S-3.0M6-20080404175400
- WTP 3.0 M6 New and Noteworthy
WTP 3.0
March 31, 2008 - April 07, 2008
- WTP 3.0 M6 Milestone build S-3.0M6-20080404175400
- Please note that the "all in ones" will be available on 4/15 and Ganymede's M6 release date is 4/16.
- New Help for Old Friends III (Note the large number of removed resources in J2EE)
- Plugin Version Information
- Noteworthy mailing list posts
- Information on P2
- JSF Tools Plugins: Incrementing minor version
- Changes to Web services tools in M6
- Changes in version number for command.env.ui and wst.ws plugin
- New versions for Validation Framework plug-ins
- New versions for Faceted Project Framework plugins
- Platform fix for displaying proper resource icons in the navigator/project explorer
- Server plugin version changes - next week
- DependencyGraphManager Job changes
- Server tools job changes
- New features in Faceted Project Framework
- Dali naming convention for getter methods
References
Previous Adopter Breakage Report Information
- Details
- org.eclipse.jst.jsf.context.resolver.structureddocument.internal.impl.MetadataContextResolver was renamed to org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.
- In org.eclipse.wst.server.ui.internal.Messages, the fields host,name,vendor, and version were removed.
- In the internal package, org.eclipse.wst.server.core.internal, deprecated classes ModuleEvent, ModuleFactoryEvent, and IModuleListener were removed.
- In the internal class org.eclipse.wst.server.core.internal.ServerPlugin, getModuleArtifact(...) was removed.
- In the internal class, org.eclipse.jst.j2ee.internal.common.operations.JavaModelUtil, the method findType(..) changed arguments. This class is basically a copy of a JEM class to avoid adding a JEM dependency, and to keep up with changes in JEM, this class was updated.
- In org.eclipse.wst.wsdl.binding.soap.SOAPHeader and org.eclipse.wst.wsdl.binding.soap.SOAPHeaderFault, the methods getPart(...), setPart(...), getMessage(...), setMessage(...) were replaced by new methods. Details:
- The WSDL model SOAPHeader and SOAPAddress classes should have been inheriting the WSDL4J interfaces but weren't. Unfortunately the javax.wsdl interface already defines getMessage() and getPart () using a different signature. So this is a case where in order to 'fix' our model to make it comply with the WSDL4J we needed to break the 'provisional API' (these classes specified api=false in the component.xml file). Current clients will simply need to change references from getPart or getMessage to getEPart and getEMessage to access the EMF equivalent classes.