Yeah, I figured it was auto-generated. I wanted to match the existing style without losing Dan's descriptive text.
On Mon, Dec 27, 2010 at 10:38 AM, Howard Lewis Ship <[email protected]>wrote: > Josh, > > The HTML for all issues is generated by JIRA when the release is created; > it's part of the release process. The manual text is to highlight features > that may get lost in the shuffle, or may cause upgrade problems. > > > On Sun, Dec 26, 2010 at 12:26 PM, <[email protected]> wrote: > >> Release Notes >> 5.3.0<https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Notes+5.3.0> >> Page >> *edited* by Josh >> Canfield<https://cwiki.apache.org/confluence/display/~joshcanfield> >> *Comment:* Added note about generic properties >> >> Changes (2) >> {html} >> >> <h2>Feature</h2> >> <ul> >> <li>[<a href='https://issues.apache.org/jira/browse/TAP5-742'>TAP5-742</a>] >> - Add optional component tracing comments to rendered output >> <div> >> It is now possible to have Tapestry emit rendering comments; these are >> comments (such as {{<!\-\-BEGIN Index:loop (context:Index.tml, line >> 15)\-\->}}) that can assist you in debugging markup output on the >> client-side. This is enabled for all requests using the configuration symbol >> {{tapestry.component-render-tracing-enabled}}, and can be added to any >> request by adding the query parameter {{t:component-trace=true}} to the URL. >> This will significantly increase the size of the rendered markup, but can be >> very helpful with complex layouts to determine which component was >> responsible for which portion of the rendered page. >> <div> >> </li> >> <li>[<a href='https://issues.apache.org/jira/browse/TAP5-1389'>TAP5-1389</a>] >> - Access properties of generic page and component fields</li> >> </ul> >> >> >> {html} >> Full Content >> Feature >> >> - [TAP5-742 <https://issues.apache.org/jira/browse/TAP5-742>] - Add >> optional component tracing comments to rendered output >> It is now possible to have Tapestry emit rendering comments; these are >> comments (such as {{}}) that can assist you in debugging markup output on >> the client-side. This is enabled for all requests using the configuration >> symbol {{tapestry.component-render-tracing-enabled}}, and can be added to >> any request by adding the query parameter {{t:component-trace=true}} to >> the >> URL. This will significantly increase the size of the rendered markup, but >> can be very helpful with complex layouts to determine which component was >> responsible for which portion of the rendered page. >> - [TAP5-1389 <https://issues.apache.org/jira/browse/TAP5-1389>] - >> Access properties of generic page and component fields >> >> Change Notification >> Preferences<https://cwiki.apache.org/confluence/users/viewnotifications.action> >> View >> Online<https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Notes+5.3.0>| >> View >> Changes<https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=24190989&revisedVersion=3&originalVersion=2> >> > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com >
