Author: max.andersen(a)jboss.com Date: 2011-09-14 13:40:26 -0400 (Wed, 14 Sep 2011) New Revision: 34736 Modified: trunk/documentation/whatsnew/cdi/cdi-news-3.3.0.M3.html trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html trunk/documentation/whatsnew/vpe/vpe-news-3.3.0.M3.html Log: JBIDE-9610 typos/grammar/sanity Modified: trunk/documentation/whatsnew/cdi/cdi-news-3.3.0.M3.html =================================================================== --- trunk/documentation/whatsnew/cdi/cdi-news-3.3.0.M3.html 2011-09-14 17:39:03 UTC (rev 34735) +++ trunk/documentation/whatsnew/cdi/cdi-news-3.3.0.M3.html 2011-09-14 17:40:26 UTC (rev 34736) @@ -47,7 +47,7 @@ <li>Stereotype/Qualifier/Scope annotation type must be annotated with @Retention(RUNTIME)</li> <li>Qualifier annotation type must be annotated with @Target('{'TYPE, METHOD, FIELD, PARAMETER'}') or @Target('{'FIELD, PARAMETER'}') [JSR-299 2.3.2, 10.1]</li> <li>Scope annotation type must be annotated with @Target('{'TYPE, METHOD, FIELD'}') [JSR-299 2.4.2]</li> - <li>Quick fix for "Stereotype declares a non-empty @Named annotation [JSR-299 2.7.1.3]</li> + <li>Stereotype declares a non-empty @Named annotation [JSR-299 2.7.1.3]</li> <li>Interceptor/Decorator has a name [JSR-299 2.5.3]</li> <li>Stereotype cannot be annotated @Typed [JSR-299 2.7.1.3]</li> <li>Annotation-valued or array-valued member of a qualifier or interceptor binding type must be annotated @Nonbinding [JSR-299 5.2.5, 9.5.2]</li> @@ -221,7 +221,7 @@ <p><b>Seam Servlet</b></p> </td> <td align="top"> - <p>Injection points annotated @RequestParam/@HeaderParam/@CookieParam are now ignored by CDI validator since it's imposible in design time to know what bean will be injected to this point.</p> + <p>Injection points annotated @RequestParam/@HeaderParam/@CookieParam are now ignored by CDI validator since it's imposible in design time to know what bean will be injected.</p> <p> <small> <a href="https://issues.jboss.org/browse/JBIDE-9389">Related Jira JBIDE-9389</a> Modified: trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html =================================================================== --- trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html 2011-09-14 17:39:03 UTC (rev 34735) +++ trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html 2011-09-14 17:40:26 UTC (rev 34736) @@ -40,9 +40,17 @@ <p><b>@ManagedBean support</b></p> </td> <td valign="top"> - <p>JSF Tools now support managed beans annotated @ManagedBean. This support includes EL code completion, validation, refactoring, OpenOns (Ctrl+Click) and searching (Ctrl+Shift+G).</p> + <p>JSF Tools now support managed beans annotated + @ManagedBean. This support includes EL code + completion, validation, refactoring, OpenOns + (Ctrl+Click) and searching (Ctrl+Shift+G).</p> + <img src="images/3.3.0.M3/ca.png"/> - <p><small><a + <p>Wwith this existing + applications and examples will no longer have error + markers for EL expressions that refer to + @ManagedBeans. For new development consider use CDI + beans with @Named instead for fuller integration.</p><p><small><a href="https://jira.jboss.org/browse/JBIDE-5045">Related Jira</a></small></p> </td> </tr> @@ -58,7 +66,8 @@ <p><b>&lt;faces-config metadata-complete="true"&gt;</b></p> </td> <td valign="top"> - <p>If &lt;faces-config metadata-complete="true"&gt; then JSF Tools will ignore bean annotated @ManagedBean according to JSF-2 spec.</p> + <p> <code>&lt;faces-config + metadata-complete="true"&gt;</code> in faces-config.xml JSF Tools will ignore bean annotated @ManagedBean according to JSF-2 spec.</p> <p><small><a href="https://jira.jboss.org/browse/JBIDE-8280">Related Jira</a></small></p> </td> </tr> @@ -76,44 +85,78 @@ </td> <td valign="top"> <p> - It was a pretty annoying bug in <b>Add JSF Capability</b> dialog which required web.xml. That obsolete dialog has been removed. Now all you need to enable JBoss JSF Tools support is to install JSF facet into the project. - So Project->Configuration->Add JSF Capability will lead you to Project Properties->Facets property page. Web.xml is not required there. + <b>Add JSF Capability</b> dialog which were + used to enable JSF on projects required an web.xml + even for JavaEE projects. That limitation and dialog + has now been removed. Now all you need to enable JBoss + JSF Tools support is to install JSF facet into the + project and things will just work. + </p> + <p>Project->Configuration->Add JSF Capability will + lead you to Project Properties->Facets property + page. Web.xml is not required for this. </p> + <p> <small> <a href="https://jira.jboss.org/browse/JBIDE-9198">Related Jira</a> </small> </p> - <p> - If some of your JSF project depends on another Java Project then both project should have JBoss Tools Knowledge Base builder installed to provide code completion, validation and other features for all resources from both projects. - If for some reason not all of your dependent projects configured correctly then JBoss Tools will add a warning to the project. A QuickFix is available for such a warning. And of course you can disable that warning in Preferences. + + </td> + </tr> + + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Resources in related non-WTP projects</b></p> + </td> + <td valign=top> + <p>If you project have resources in related + projects which does not have JBoss Tools Knowledgebase + Builder installed JBoss Tools cannot "see" the + resources inside these projects and you might get + false warnings.</p> + + <p>To help avoid this problem JBoss Tools now warns + if it detects project dependencies + which should have the knowledgebase + builder enabled to make it visible to + JBoss Tools and be available in code + completion, validation and resource lookups.</p> + + <p>A QuickFix is available for the warning so it is + easy to fix and of course if you do not wish + your projects to have the build you can + disable the Warning in Preferences. </p> <img src="images/3.3.0.M3/qf.png"/> <p> - <small> - <a href="https://jira.jboss.org/browse/JBIDE-9120">Related Jira</a> - </small> + It is also possible to enable the + support via project properties page: </p> - <p> - Also it's possible to enable such a support via project properties page: - </p> <img src="images/3.3.0.M3/properties.png"/> <p> + If you missed the warning you will be + asked to fix the configuration problem when + you are opening any XHTML or JSP page with + JBoss Tools Visual Page Editor. </p> - <p> - <small> - <a href="https://jira.jboss.org/browse/JBIDE-9198">Related Jira</a> - </small> - </p> - <p> - If you missed the warning you will be asked to fix the configuration problem when you are opening any XHTML or JSP page with JBoss Tools Visual Page Editor. - </p> <img src="images/3.3.0.M3/nature.png"/> <p> <small> - <a href="https://jira.jboss.org/browse/JBIDE-9427">Related Jira</a> + Related jira <a + href="https://jira.jboss.org/browse/JBIDE-9120">1</a>,... + href="https://jira.jboss.org/browse/JBIDE-9198">2</a>,... + href="https://jira.jboss.org/browse/JBIDE-9427">3</a> + </small> </p> + </td> </tr> Modified: trunk/documentation/whatsnew/vpe/vpe-news-3.3.0.M3.html =================================================================== --- trunk/documentation/whatsnew/vpe/vpe-news-3.3.0.M3.html 2011-09-14 17:39:03 UTC (rev 34735) +++ trunk/documentation/whatsnew/vpe/vpe-news-3.3.0.M3.html 2011-09-14 17:40:26 UTC (rev 34736) @@ -39,26 +39,34 @@ <tr> <td valign="top" align="left" width="200px"> <b><p> - Special and non-ASCII characters is now supported in Externalize Strings wizard + non-ASCII characters in Externalize Strings wizard <p></b> </td> <td valign="top"> - <p>Line breaks and carret returns are displayed as escaped sequence.</p> - <p>As well as non-ASCII characters are shown in unicode codes.</p> + <p>Line breaks and carriage returns are now displayed + as escaped sequence and non-ASCII characters are shown in unicode codes.</p> <p><img src="images/3.3.0.M3/9203.png" alt="non-ASCII characters" /></p> <p><small> <a href="https://jira.jboss.org/jira/browse/JBIDE-9203">Related Jira</a> </small></p> </td> </tr> + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> <tr> <td valign="top" align="left" width="200px"> <b><p> - Default "Actual Run-Time Folders" are shown in the Page Desigh Options dialog + Default "Actual Run-Time Folders" are shown in the Page Design Options dialog <p></b> </td> <td valign="top"> - <p>Checkboxes were added to change default value</p> + <p>The default values are now shown in the Page Design + dialog letting you know what folders absolute and relative + folders are for. To change the default value use the checkbox + to enable editing of the fields.</p> <p><img src="images/3.3.0.M3/8719.png" alt="Actual Run-Time Folders" /></p> <p><small> <a href="https://jira.jboss.org/jira/browse/JBIDE-8719">Related Jira</a>