<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">6</component-id>
  <created-on type="datetime">2011-12-08T00:56:33-05:00</created-on>
  <description>On Ubuntu 10.04, running scalate commands directly from the command line seems to never finish.  It's not burning CPU or anything, though.

&lt;pre&gt;&lt;code&gt;$ cat index.jade
!!!
html
 head
   title Price series browser
   link(rel='stylesheet' type='text/css' href='main.css')
 body
   #canvas
   script(src='https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js')
   script(src='http://mbostock.github.com/d3/d3.js?2.6.0')
   script(src='http://documentcloud.github.com/underscore/underscore-min.js')
   script(src='http://epeli.github.com/underscore.string/dist/underscore.string.min.js')
   script(src='main.js')

$ scalate run index.jade
(nothing happens; same thing with scalate 'run index.jade')
^C
&lt;/code&gt;&lt;/pre&gt;

But when I run 'run index.jade' from the scalate REPL, it spits out the rendered template.

Also, may or may not be related, but 'exit' (or ^D) sometimes hangs as well.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">11131383</id>
  <importance type="integer">278</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>bIvREuUMWr3irVabIlDkbG</notification-list>
  <number type="integer">278</number>
  <priority type="integer">2</priority>
  <reporter-id>bIvREuUMWr3irVabIlDkbG</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scalate tool 1.5.3 hanging</summary>
  <updated-at type="datetime">2012-04-11T11:51:24-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bIvREuUMWr3irVabIlDkbG</id><login>yaaang</login><login_name warning="deprecated">yaaang</login_name><name>Yang Zhang</name><organization>MIT</organization><website>http://yz.mit.edu/</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">10</component-id>
  <created-on type="datetime">2012-03-28T13:15:29-04:00</created-on>
  <description>It would be nice if scalate's implementation of mustache behaved the same way as other implementations.
Currently, the block is prerendered and passed to the lambda function, and whatever is returned from the function is the final output.
This is almost exactly the opposite of what it should be:

http://mustache.github.com/mustache.5.html

Lambdas

When the value is a callable object, such as a function or lambda, the object will be invoked and passed the block of text. The text passed is the literal block, unrendered. {{tags}} will not have been expanded - the lambda should do that on its own. In this way you can implement filters or caching.

Template:

{{#wrapped}}
  {{name}} is awesome.
{{/wrapped}}

Hash:

{
  &quot;name&quot;: &quot;Willy&quot;,
  &quot;wrapped&quot;: function() {
    return function(text) {
      return &quot;&lt;b&gt;&quot; + render(text) + &quot;&lt;/b&gt;&quot;
    }
  }
}

Output:

&lt;b&gt;Willy is awesome.&lt;/b&gt;
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">17828743</id>
  <importance type="integer">282</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>bgkYZ-EpGr4A7BacwqjQWU</notification-list>
  <number type="integer">282</number>
  <priority type="integer">2</priority>
  <reporter-id>bgkYZ-EpGr4A7BacwqjQWU</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scalate Mustache Lamda's do not follow the Mustache Spec for Lambda Functions</summary>
  <updated-at type="datetime">2012-03-28T13:15:29-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgkYZ-EpGr4A7BacwqjQWU</id><login>kdavis80</login><login_name warning="deprecated">kdavis80</login_name><name>kdavis80</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>cGhdVOfnqr34N5eJe5afGb</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-08-06T09:43:09-04:00</created-on>
  <description>We have the elvis operator for dealing with nulls on an expression
&lt;pre&gt;&lt;code&gt;foo ?: &quot;default value&quot;&lt;/code&gt;&lt;/pre&gt;
however this doesnt work when you want to do 
&lt;pre&gt;&lt;code&gt;foo.bar.whatnot&lt;/code&gt;&lt;/pre&gt;
the code is messy.  So a helper method something like
&lt;pre&gt;&lt;code&gt;orElse(foo.bar.whatnot, &quot;default value&quot;)&lt;/code&gt;&lt;/pre&gt;
might help - catching NullPointerExceptions along the way for you (with maybe debug logging if you want to search and find them)



</description>
  <from-support type="integer">1</from-support>
  <id type="integer">1858255</id>
  <importance type="integer">124</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">124</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>add helper method for dealing with navigating through legacy java object graphs which might throw NullPointerException</summary>
  <updated-at type="datetime">2010-09-09T15:00:38-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-08-06T10:14:14-04:00</created-on>
  <description>    -@ import com.bozzio.joysteer.HtmlWriter._


i.e. using an import statement with @ rather than 

  - import foo.bar.Whatnot._

</description>
  <from-support type="integer">1</from-support>
  <id type="integer">1858453</id>
  <importance type="integer">125</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">125</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>this should give a more meaningful error...</summary>
  <updated-at type="datetime">2010-08-24T12:49:30-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-08-24T10:19:18-04:00</created-on>
  <description>we have request scoped attribute variables in attributes* methods; we should have similar equivalents for request parameters and their session scoped equivalent using the Http Session object. e.g. so in a template we could do...

&lt;pre&gt;&lt;code&gt;
${params.getOrNull(&quot;myParam&quot;, &quot;defaultValue&quot;)}
&lt;/code&gt;&lt;/pre&gt;



</description>
  <from-support type="integer">1</from-support>
  <id type="integer">1993963</id>
  <importance type="integer">139</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,bZWxgUjSyr354reJe5avMc</notification-list>
  <number type="integer">139</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>support session scoped variables in a helper method on the ServletRenderContext for use in web apps</summary>
  <updated-at type="datetime">2012-05-18T06:38:31-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-08-26T06:53:07-04:00</created-on>
  <description>e.g. something like...

&lt;form action=&quot;/foo/bar&quot; method=&quot;post&gt;
  ${textField(&quot;name&quot;, customer.name)}
  ${textArea(&quot;comments&quot;, comments)}
&lt;/form&gt;

so folks can avoid lots of the laborious coding for these things</description>
  <from-support type="integer">1</from-support>
  <id type="integer">2005437</id>
  <importance type="integer">145</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">145</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>provide some helper functions to create forms easily from a domain model in a template</summary>
  <updated-at type="datetime">2010-08-26T06:53:07-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">7</component-id>
  <created-on type="datetime">2010-09-07T06:20:24-04:00</created-on>
  <description>so we can auto-create various pages like the versions index page, the download page links etc This then saves manual editing of various bits of the website as releases happen.

should we maybe use the pom.xml versions? or grep the changelog? Or some separate file? </description>
  <from-support type="integer">0</from-support>
  <id type="integer">2058479</id>
  <importance type="integer">147</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">147</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>have a way to enumerate through all the released version numbers using some text file</summary>
  <updated-at type="datetime">2010-09-07T06:20:24-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-09-15T04:56:48-04:00</created-on>
  <description>e.g. 

&lt;!-- [START template=/MyClass.head.scaml --&gt;
...
&lt;!--[END template=/MyClass.head.scaml --&gt;
...


more detail here...
http://groups.google.com/group/scalate/browse_thread/thread/437643ad011e944f</description>
  <from-support type="integer">1</from-support>
  <id type="integer">2102237</id>
  <importance type="integer">159</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">159</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>support tracing comments in output so you can see what output came from what template</summary>
  <updated-at type="datetime">2010-09-15T04:56:48-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-09-27T10:52:04-04:00</created-on>
  <description>e.g. the major differences are the static typing, how the layout works and what binding attributes means etc</description>
  <from-support type="integer">0</from-support>
  <id type="integer">2167439</id>
  <importance type="integer">161</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">161</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>create a scaml/jade for haml/jade section in the docs to get folks who grok haml/jade up to speed quickly</summary>
  <updated-at type="datetime">2011-02-09T08:11:02-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-11-08T07:33:02-05:00</created-on>
  <description>e.g.

cd samples/scalate-sample
mvn jetty:run

then open:
http://localhost:8080/bad

its currently showing the stack trace but not showing the nice Scalate console</description>
  <from-support type="integer">1</from-support>
  <id type="integer">2508635</id>
  <importance type="integer">181</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">181</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>JAXRS Scalate renderer which finds error on template does not use the Scalate error page to show the error</summary>
  <updated-at type="datetime">2010-11-08T07:33:02-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-11-25T04:05:53-05:00</created-on>
  <description>if we have some text like &quot;this &amp;amp; that&quot; then by default we escape the &amp; to &quot;this &amp;amp;amp; that&quot; which is a bit silly. I wonder if we should by default auto-detect entity references in the markup/text and not escape them?

see the discussion here: http://groups.google.com/group/scalate/browse_thread/thread/6231fc39c6f769b8</description>
  <from-support type="integer">2</from-support>
  <id type="integer">2619579</id>
  <importance type="integer">184</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">184</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>should the markup escaping code auto-detect entity references and avoid escaping them?</summary>
  <updated-at type="datetime">2012-04-17T00:13:06-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">5</component-id>
  <created-on type="datetime">2011-02-10T07:44:29-05:00</created-on>
  <description>each time we release, we update the blog post like this one...
http://scalate.fusesource.org/blog/releases/release-1-4-0.html

then copy the relevant markdown into here...
https://github.com/scalate/scalate/blob/master/changelog.md

then make a plain text email to send to the mailing list...
http://groups.google.com/group/scalate/browse_thread/thread/5c02e49f2b9a18e4

all of which has the same generic shape (template) the only thing that really changes is the version number, URL of the change log and the markdown text section.

I wonder if we can hack up a little plugin that does this work? generate the HTML file for the blog post, plain text and auto-prepend the changelog? Am sure other projects could reuse it too?
</description>
  <from-support type="integer">2</from-support>
  <id type="integer">3115809</id>
  <importance type="integer">212</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">212</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>announce plugin for releasing?</summary>
  <updated-at type="datetime">2011-02-10T07:44:29-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-04-01T14:50:49-04:00</created-on>
  <description>The user guide says that the samples require Maven 2.0.9 or higher. Here's what I get:


$&gt; /usr/bin/mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_22
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: &quot;mac os x&quot; version: &quot;10.6.6&quot; arch: &quot;x86_64&quot; Family: &quot;mac&quot;

$&gt; /usr/bin/mvn install
[INFO] Scanning for projects...
[WARNING] POM for 'biz.aQute:bndlib:pom:1.15.0:runtime' is invalid.

Its dependencies (if any) will NOT be available to the current build.
[INFO] ------------------------------------------------------------------------
[INFO] Building scalate-sample
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error resolving version for 'org.apache.maven.plugins:maven-site-plugin': Plugin requires Maven version 3.0
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Apr 01 14:43:37 EDT 2011
[INFO] Final Memory: 24M/81M
[INFO] ------------------------------------------------------------------------
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3523695</id>
  <importance type="integer">231</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>csNKVWxjar4lhfeJe5cbLA</notification-list>
  <number type="integer">231</number>
  <priority type="integer">3</priority>
  <reporter-id>csNKVWxjar4lhfeJe5cbLA</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>scalate-sample fails to build with mvn2</summary>
  <updated-at type="datetime">2011-04-01T14:50:49-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>csNKVWxjar4lhfeJe5cbLA</id><login>psfblair</login><login_name warning="deprecated">psfblair</login_name><name>psfblair</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-04-06T22:24:00-04:00</created-on>
  <description>I believe that the TemplateEngineFilter is currently swallowing the HTTP response, in that any other filters defined in web.xml *after* TemplateEngineFilter don't get a chance to process the response. Instead, the TemplateEngineFilter should call chain.doFilter(request_wrapper, response_wrapper).</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3563417</id>
  <importance type="integer">234</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list></notification-list>
  <number type="integer">234</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Allow other servlet filters to process response</summary>
  <updated-at type="datetime">2011-11-14T17:31:08-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-04-26T05:45:03-04:00</created-on>
  <description></description>
  <from-support type="integer">2</from-support>
  <id type="integer">3703534</id>
  <importance type="integer">236</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,bEw1VyeQOr4lzUeJe5cbLr,bZWxgUjSyr354reJe5avMc</notification-list>
  <number type="integer">236</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>provide i18n helper methods for rendering text from resource bundles based on the locale</summary>
  <updated-at type="datetime">2012-05-18T06:39:28-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-04-26T05:46:06-04:00</created-on>
  <description>e.g. for a request for &quot;foo/bar&quot; we could look for foo/bar.en.uk.ssp or foo/bar.en.ssp or foo/bar.ssp (depending on the Locale) rather like how i18n bundles work.
</description>
  <from-support type="integer">2</from-support>
  <id type="integer">3703542</id>
  <importance type="integer">237</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">237</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>support searching for templates using the current Locale's language and location like the resource bundles works for i18n</summary>
  <updated-at type="datetime">2011-04-26T05:46:06-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-05-08T04:35:02-04:00</created-on>
  <description>http://stackoverflow.com/questions/5918684/scaml-illegal-nesting-error

I was confused at first reading it until I saw the answer :) Wonder if we could detect there's content on the same line and nested content or something?</description>
  <from-support type="integer">2</from-support>
  <id type="integer">3801180</id>
  <importance type="integer">241</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">241</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>wonder if we could use a more obvious error message for using nested and same line...</summary>
  <updated-at type="datetime">2011-05-08T04:35:02-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-06-01T10:55:37-04:00</created-on>
  <description>Considering the template below:
&lt;pre&gt;&lt;code&gt;
!!!
%html
  %head
    %title Some title
%body
  %p Some text in greek (&#922;&#945;&#955;&#951;&#963;&#960;&#941;&#961;&#945;)
&lt;/code&gt;&lt;/pre&gt;
I can't get the greek work right. As I can see from the generated source code the greek characters was escaped, so I used &lt;code&gt;= &quot;Some text in greek (&#922;&#945;&#955;&#951;&#963;&#960;&#941;&#961;&#945;)&quot;&lt;/code&gt; instead and the generated scala file did have the right characters. Still in both situations I can't get the template get rendered right (the output html contains ? instead of greek characters).

I had similar problems with groovy and -Dfile.encoding=UTF-8 did solve the problem so I made sure this system property had UTF-8 as value.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">4054578</id>
  <importance type="integer">245</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>dnEtwaJf0r4kXceJe5cbCb</notification-list>
  <number type="integer">245</number>
  <priority type="integer">3</priority>
  <reporter-id>dnEtwaJf0r4kXceJe5cbCb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Uft-8 encoded scaml doesn't render right</summary>
  <updated-at type="datetime">2011-09-11T14:04:38-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dnEtwaJf0r4kXceJe5cbCb</id><login>valotas</login><login_name warning="deprecated">valotas</login_name><name>valotas</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-06-06T16:26:36-04:00</created-on>
  <description>This occurs in Scalate 1.4.1. Using { } braces within a string used for an attribute value seems to confuse the scaml parser. For example:
&lt;pre&gt;&lt;code&gt;
%element{:foo =&gt; {&quot;function(){}&quot;}}
&lt;/code&gt;&lt;/pre&gt;
The exception is:
&lt;pre&gt;&lt;code&gt;
org.fusesource.scalate.InvalidSyntaxException: `}' expected but `&quot;' found at 1.32
	at org.fusesource.scalate.scaml.ScamlParser.parse(ScamlParser.scala:375)
	at org.fusesource.scalate.scaml.ScamlCodeGenerator.generate(ScamlCodeGenerator.scala:668)
	at org.fusesource.scalate.TemplateEngine.compileAndLoad(TemplateEngine.scala:684)
	at org.fusesource.scalate.TemplateEngine.compileAndLoadEntry(TemplateEngine.scala:637)
	at org.fusesource.scalate.TemplateEngine.liftedTree1$1(TemplateEngine.scala:368)
	at org.fusesource.scalate.TemplateEngine.load(TemplateEngine.scala:362)
	at org.fusesource.scalate.TemplateEngine.load(TemplateEngine.scala:432)
	at org.fusesource.scalate.RenderContext$$anonfun$render$1$$anonfun$apply$mcV$sp$1.apply(RenderContext.scala:367)
	at org.fusesource.scalate.RenderContext$$anonfun$render$1$$anonfun$apply$mcV$sp$1.apply(RenderContext.scala:367)
	at org.fusesource.scalate.RenderContext$class.withUri(RenderContext.scala:423)
	at org.fusesource.scalate.DefaultRenderContext.withUri(DefaultRenderContext.scala:30)
	at org.fusesource.scalate.RenderContext$$anonfun$render$1.apply(RenderContext.scala:366)
	at org.fusesource.scalate.RenderContext$$anonfun$render$1.apply(RenderContext.scala:366)
	at org.fusesource.scalate.RenderContext$class.withAttributes(RenderContext.scala:397)
	at org.fusesource.scalate.DefaultRenderContext.withAttributes(DefaultRenderContext.scala:30)
	at org.fusesource.scalate.RenderContext$class.render(RenderContext.scala:365)
	at org.fusesource.scalate.DefaultRenderContext.render(DefaultRenderContext.scala:30)
&lt;/code&gt;&lt;/pre&gt;
It looks like the use of the braces for expression evaluation is what causes the problem. The following will work fine:
&lt;pre&gt;&lt;code&gt;
%element{:foo =&gt; &quot;function(){}&quot;}
&lt;/code&gt;&lt;/pre&gt;
One workaround would be to introduce a variable within the page to store the string value I want, and then use that variable as the attribute's value.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">4094466</id>
  <importance type="integer">246</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>b-4KkQVpur346SeJe5cbLA</notification-list>
  <number type="integer">246</number>
  <priority type="integer">3</priority>
  <reporter-id>b-4KkQVpur346SeJe5cbLA</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scaml: element attribute value cannot contain curly braces</summary>
  <updated-at type="datetime">2011-06-06T16:26:36-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>b-4KkQVpur346SeJe5cbLA</id><login>ternary.expression</login><login_name warning="deprecated">ternary.expression</login_name><name>ternary.expression</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-06-09T03:45:45-04:00</created-on>
  <description>See: https://groups.google.com/d/msg/scalate/HT3PwMIuHoo/ZogNYaZkbMkJ</description>
  <from-support type="integer">2</from-support>
  <id type="integer">4119930</id>
  <importance type="integer">247</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">247</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>maven plugin not detecting partials when precompiling?</summary>
  <updated-at type="datetime">2011-06-09T03:45:45-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-07-26T17:52:06-04:00</created-on>
  <description>I'm getting this exception from including an (empty) :sass block:


&lt;pre&gt;&lt;code&gt;&lt;script&gt;:31: undefined method `append' for nil:NilClass
(NoMethodError) (of class java.lang.String)

at org.fusesource.scalate.jruby.Sass.filter(Sass.scala:70)
at org.fusesource.scalate.RenderContext$class.filter(RenderContext.scala:275)
at org.fusesource.scalate.DefaultRenderContext.filter(DefaultRenderContext.scala:30)
at org.fusesource.scalate.RenderContext$class.value(RenderContext.scala:234)
at org.fusesource.scalate.DefaultRenderContext.value(DefaultRenderContext.scala:30)
at scalate.templates.$_scalate_$hello$dashscalate_jade$.$_scalate_$render(hello-scalate.jade.scala:35)
at scalate.templates.$_scalate_$hello$dashscalate_jade.render(hello-scalate.jade.scala:62)
at org.fusesource.scalate.RenderContext$$anonfun$render$1$$anonfun$apply$mcV$sp$1.apply$mcV$sp(RenderContext.scala:390)
at org.fusesource.scalate.RenderContext$$anonfun$render$1$$anonfun$apply$mcV$sp$1.apply(RenderContext.scala:390)
at org.fusesource.scalate.RenderContext$$anonfun$render$1$$anonfun$apply$mcV$sp$1.apply(RenderContext.scala:390)
at org.fusesource.scalate.RenderContext$class.withUri(RenderContext.scala:446)
at org.fusesource.scalate.DefaultRenderContext.withUri(DefaultRenderContext.scala:30)
at org.fusesource.scalate.RenderContext$$anonfun$render$1.apply$mcV$sp(RenderContext.scala:389)
at org.fusesource.scalate.RenderContext$$anonfun$render$1.apply(RenderContext.scala:389)
at org.fusesource.scalate.RenderContext$$anonfun$render$1.apply(RenderContext.scala:389)
at org.fusesource.scalate.RenderContext$class.withAttributes(RenderContext.scala:420)
at org.fusesource.scalate.DefaultRenderContext.withAttributes(DefaultRenderContext.scala:30)
at org.fusesource.scalate.RenderContext$class.render(RenderContext.scala:388)
at org.fusesource.scalate.DefaultRenderContext.render(DefaultRenderContext.scala:30)
at org.scalatra.scalate.ScalateSupport$class.renderTemplate(ScalateSupport.scala:44)
...

&lt;/code&gt;&lt;/pre&gt;

The source:


&lt;pre&gt;&lt;code&gt; def filter(context: RenderContext, content: String) = {

   val sassPaths = List[String]()
   var result: StringBuffer = new StringBuffer
   jruby.put(&quot;@result&quot;, result)
   jruby.run(
     &quot;require 'haml-3.0.25/lib/sass'&quot;,
     &quot;options = {}&quot;,
     &quot;options[:load_paths] = [&quot;+sassPaths.map(&quot;'&quot;+_+&quot;'&quot;).mkString(&quot;,&quot;)+&quot;]&quot;,
     &quot;options[:cache_location] = '&quot;+engine.workingDirectory+&quot;/sass'&quot;,
     &quot;options[:style] = &quot; + (if (engine.isDevelopmentMode)
&quot;:expanded&quot; else &quot;:compressed&quot;) + &quot;&quot;,
     &quot;options[:line_comments] = &quot; + (if (engine.isDevelopmentMode)
&quot;true&quot; else &quot;false&quot;) + &quot;&quot;,
     &quot;options[:syntax] = :&quot;+syntax,
     &quot;content = &lt;&lt;SCALATE_SASS_EOF\n&quot;+content+&quot;\nSCALATE_SASS_EOF&quot;,
     &quot;tree = ::Sass::Engine.new(content, options).to_tree&quot;,
     &quot;@result.append(tree.render)&quot;) match {
     case Right(result) =&gt; result.toString
     case Left((exception, errors)) =&gt;
       val err1 = &quot;&quot;&quot;(?m)([a-zA-Z_0-9-]+[.]s[ca]ss:\d+:.+)$&quot;&quot;&quot;.r
       val err2 = &quot;&quot;&quot;([(]s[ca]ss[)]:\d+:.+)$&quot;&quot;&quot;.r
       errors match {
         case err1(msg) =&gt; throw new TemplateException(msg, exception)
         case err2(msg) =&gt; throw new TemplateException(msg, exception)
       }
       throw new TemplateException(errors, exception)
   }
 }

&lt;/code&gt;&lt;/pre&gt;

So the @result.append seems to be the culprit.

The problem appears to be due to my using:


&lt;pre&gt;&lt;code&gt;renderTemplate(&quot;WEB-INF/scalate/templates/hello-scalate.jade&quot;)

&lt;/code&gt;&lt;/pre&gt;

instead of (note the leading slash):


&lt;pre&gt;&lt;code&gt;renderTemplate(&quot;/WEB-INF/scalate/templates/hello-scalate.jade&quot;)

&lt;/code&gt;&lt;/pre&gt;

Not sure how this is manifesting itself in the given exception,
though, especially since on removing the :sass block everything works.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">4545764</id>
  <importance type="integer">254</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>bIvREuUMWr3irVabIlDkbG</notification-list>
  <number type="integer">254</number>
  <priority type="integer">3</priority>
  <reporter-id>bIvREuUMWr3irVabIlDkbG</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>&lt;script&gt;:31: undefined method `append' for nil:NilClass</summary>
  <updated-at type="datetime">2011-07-26T17:52:06-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bIvREuUMWr3irVabIlDkbG</id><login>yaaang</login><login_name warning="deprecated">yaaang</login_name><name>Yang Zhang</name><organization>MIT</organization><website>http://yz.mit.edu/</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">11</component-id>
  <created-on type="datetime">2011-08-23T19:25:36-04:00</created-on>
  <description>Simply using &quot;extends DefaultWebProject(info) with PrecompilerWebProject&quot; on my SBT project was leading to irregular results, where the output template .class files would usually not get into my .war, but sometimes would, especially after I touched a .scala file and re-published. Generally, the .class files would get built, but then the prepare-webapp step would delete them.

The fine folks on #scalatra channel suggested this line in my Project:
&lt;pre&gt;&lt;code&gt;  override def precompileTemplatesAction = super.precompileTemplatesAction dependsOn prepareWebapp
&lt;/code&gt;&lt;/pre&gt;
This seems to successfully order the PCT step after the prepare-webapp step, and my builds have been working since.

casualjim also suggested &lt;code&gt;override def runAction = task { args =&gt; super.runAction(args) dependsOn(precompileTemplatesAction) }&lt;/code&gt;, which I did not try.

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">5332051</id>
  <importance type="integer">255</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>csT6NcYqir4lvteJe5cbLr</notification-list>
  <number type="integer">255</number>
  <priority type="integer">3</priority>
  <reporter-id>csT6NcYqir4lvteJe5cbLr</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>precompileTemplatesAction can run before prepareWebapp, which deletes its output</summary>
  <updated-at type="datetime">2011-08-23T19:25:36-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>csT6NcYqir4lvteJe5cbLr</id><login>drewp</login><login_name warning="deprecated">drewp</login_name><name>drewp</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-08-30T06:05:10-04:00</created-on>
  <description>Seems quite a few web apps / websites have this stuff in Boot...


&lt;pre&gt;&lt;code&gt;
    def filter(m:Matcher):String = {
      val filter_name = m.group(1)
      val body = m.group(2)
      engine.filter(filter_name) match {
        case Some(filter)=&gt;
          filter.filter(RenderContext(), body)
        case None=&gt; &quot;&lt;div class=\&quot;macro error\&quot;&gt;&lt;p&gt;filter not found: %s&lt;/p&gt;&lt;pre&gt;%s&lt;/pre&gt;&lt;/div&gt;&quot;.format(filter_name, body)
      }
    }

    def pygmentize(m:Matcher):String = Pygmentize.pygmentize(m.group(2), m.group(1))

    // add some macros to markdown.
    Markdown.macros :::= List(
      MacroDefinition(&quot;&quot;&quot;\{filter::(.*?)\}(.*?)\{filter\}&quot;&quot;&quot;, &quot;s&quot;, filter, true),
      MacroDefinition(&quot;&quot;&quot;\{pygmentize::(.*?)\}(.*?)\{pygmentize\}&quot;&quot;&quot;, &quot;s&quot;, pygmentize, true),
      MacroDefinition(&quot;&quot;&quot;\{pygmentize\_and\_compare::(.*?)\}(.*?)\{pygmentize\_and\_compare\}&quot;&quot;&quot;, &quot;s&quot;, pygmentize, true)
    )

    // add some more recognized pipelines.
    for( ssp &lt;- engine.filter(&quot;ssp&quot;); md &lt;- engine.filter(&quot;markdown&quot;) ) {
      engine.pipelines += &quot;ssp.md&quot;-&gt; List(ssp, md)
      engine.pipelines += &quot;ssp.markdown&quot;-&gt; List(ssp, md)
    }
&lt;/code&gt;&lt;/pre&gt;

Shouldn't this kinda stuff be added by default?</description>
  <from-support type="integer">2</from-support>
  <id type="integer">5725591</id>
  <importance type="integer">256</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">256</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>should we add the pygmentize style macros by default to markdown?</summary>
  <updated-at type="datetime">2011-08-30T06:05:10-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-09-09T09:20:57-04:00</created-on>
  <description>e.g. compiling the :coffeescript filter, we should have nicer line numbers for the real actual line numbers in the template</description>
  <from-support type="integer">0</from-support>
  <id type="integer">6233331</id>
  <importance type="integer">261</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">261</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>allow filters to have line number information of where the source comes from for better error reporting</summary>
  <updated-at type="datetime">2011-09-09T09:20:57-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">5</component-id>
  <created-on type="datetime">2011-10-20T04:28:17-04:00</created-on>
  <description>Hi there,

We've been using SSPs in our project, and want to precompile them before deploying them. We ran into an issue where the SSP would compile fine when deployed using scalatra in a container but fail to compile. 

We investigated this and we were using some objects made available by org.scalatra.ScalatraContext (specifically &quot;session&quot;). When running the pre-compile, I think it must only use the object instances made available by ServletRenderContext. 

Steps to reproduce:
* Create an SSP that refers to the &quot;session&quot; instance, or &quot;params&quot; in ScalatraContext
* Run a maven precompile

This is not a blocking issues as there are some workarounds. Namely, instead of in the SSP referring to session directly, we can use &quot;request.getSession&quot;

Let me know if you need any more information. Not sure if this is an intentional thing or not.

</description>
  <from-support type="integer">1</from-support>
  <id type="integer">8575763</id>
  <importance type="integer">268</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cfZCMS-Vqr4kBdacwqjQYw</notification-list>
  <number type="integer">268</number>
  <priority type="integer">3</priority>
  <reporter-id>cfZCMS-Vqr4kBdacwqjQYw</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Compile works when deployed, but not during precompilation when referring to 'session' in SSP</summary>
  <updated-at type="datetime">2011-10-20T04:28:17-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cfZCMS-Vqr4kBdacwqjQYw</id><login>patrick.kua</login><login_name warning="deprecated">patrick.kua</login_name><name>patrick.kua</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-10-25T10:56:25-04:00</created-on>
  <description>e.g. this causes the parser to get confused...

- escapeMarkup = false
- val expr = &quot;a() &gt; b()&quot;
td(data-bind={&quot;attr: {class: &quot; + expr + &quot; ? 'green' : 'red'}&quot;})
- escapeMarkup = true


</description>
  <from-support type="integer">1</from-support>
  <id type="integer">8818123</id>
  <importance type="integer">269</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,bIvREuUMWr3irVabIlDkbG</notification-list>
  <number type="integer">269</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>dynamic expressions in jade/scaml attributes which have Strings containing { } confuse the parser</summary>
  <updated-at type="datetime">2011-10-25T14:40:41-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-10-27T02:37:17-04:00</created-on>
  <description>Hi

I did a pull this morning and build the source according to the instructions


But after a bit I get this error. 

[ERROR] Failed to execute goal on project scalate-jrebel: Could not resolve dependencies for project org.fusesource.scalate:scalate-jrebel:jar:1.6.0-SNAPSHOT: Could not find artifact org.zeroturnaround:jr-sdk:jar:3.1.2 in central (http://repo1.maven.org/maven2) -&gt; [Help 1]

</description>
  <from-support type="integer">1</from-support>
  <id type="integer">8966303</id>
  <importance type="integer">272</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>bRTLQSV9Sr34tZeJe5cbLr</notification-list>
  <number type="integer">272</number>
  <priority type="integer">3</priority>
  <reporter-id>bRTLQSV9Sr34tZeJe5cbLr</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Build from source - Missing JRebel JAR</summary>
  <updated-at type="datetime">2011-10-27T02:39:27-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bRTLQSV9Sr34tZeJe5cbLr</id><login>claus.ibsen</login><login_name warning="deprecated">claus.ibsen</login_name><name>claus.ibsen</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-11-28T07:00:19-05:00</created-on>
  <description>Seen this not to be the case by default in WebLogic for example...</description>
  <from-support type="integer">2</from-support>
  <id type="integer">10537393</id>
  <importance type="integer">276</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">276</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>is the console compiled by default by the precompile plugin?</summary>
  <updated-at type="datetime">2011-11-28T07:00:19-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">8</component-id>
  <created-on type="datetime">2011-12-22T16:50:20-05:00</created-on>
  <description>Using {include} inside a page that sets an attribute (e.g. sets the page title) will override that attribute's value with whatever value is set in the included page.

Example: the title for the page below will be whatever the title is of the /news/recent.page instead of what is defined in the page itself

---
title: Welcome to Apache ServiceMix!
--- name:main pipeline:conf
h2. [News]
{include:/news/recent.page}
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">11903633</id>
  <importance type="integer">279</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>byBhb6Soyr35jTeJe5cbLr</notification-list>
  <number type="integer">279</number>
  <priority type="integer">3</priority>
  <reporter-id>byBhb6Soyr35jTeJe5cbLr</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Confluence {include} macro overrides original page attributes</summary>
  <updated-at type="datetime">2011-12-22T16:50:20-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>byBhb6Soyr35jTeJe5cbLr</id><login>gertv</login><login_name warning="deprecated">gertv</login_name><name>gertv</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2012-01-30T15:12:02-05:00</created-on>
  <description>The TemplateEngine.compileAndLoad() method calls the text() method of TemplateSource twice. The first call is val text = source.text (which is always called but used only by the pipeline), and the second call is on the generator generate() method which is passed the TemplateSource object. This is inefficient but it works when using an underlying File Object (as is the default situation), but when using a SourceTemplateSource to provide the template, this fails since a Scala Source can only be read once, after which it must be reset (and in some cases reset does not work either, for example if the Source is based on a stream e.g. Source.fromInputStream(...), unless the caller provides a reset function using the withReset method).

Some possible fixes / improvements:

1) Do source.reset on every call to text. This may require the caller to provide a resetFunction. The read will continue to be executed at least twice.

2) Move call to source.text into the match for pipeline, so that source is only read once unless a pipeline is used, in which case it will continue to be executed twice (still requires fix #1 above).

3) Cache the call to the text method in Resource and return the cached value if it has already been called before.

4) Ensure the code never calls source.text twice.

I have submitted https://github.com/scalate/scalate/pull/18 to implement a work-around via #1 and #2 but I suspect you may want to implement the optimal fix #3 or #4.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">13858543</id>
  <importance type="integer">280</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>at76nGtaCr4iX2eJe5cbLr</notification-list>
  <number type="integer">280</number>
  <priority type="integer">3</priority>
  <reporter-id>at76nGtaCr4iX2eJe5cbLr</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scala SourceTemplateSource read twice, second read is empty</summary>
  <updated-at type="datetime">2012-01-30T15:12:02-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>at76nGtaCr4iX2eJe5cbLr</id><login>rocketraman</login><login_name warning="deprecated">rocketraman</login_name><name>rocketraman</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-02-17T08:26:50-05:00</created-on>
  <description>I would be great if the samples were available in both pre-compiled and non-precompiled forms. That way one could quickly judge the effect pre-compilation has on performance. (You wouldn't need to duplicate the sampe projects for this; attaching a secondary artifact with &quot;recompiled&quot; classifer should do the trick.)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3161881</id>
  <importance type="integer">214</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list></notification-list>
  <number type="integer">214</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Offer pre-compiled versions of the samples as well</summary>
  <updated-at type="datetime">2011-02-17T08:26:50-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">12</component-id>
  <created-on type="datetime">2011-09-02T15:08:55-04:00</created-on>
  <description>Hi all.

After attempting to use Scalate with Spring's Portlet MVC (using scalate-spring-mvc), I've discovered that because ServletConfig/PortletConfig and ServletContext/PortletContext don't share common ancestry, it's a non-starter.

I have however adapted the TemplateEngineServlet to be compatible with Spring's InternalResourceViewResolver in a Portlet environment (see attached code). Although I'd like to contribute something like a _scalate-spring-portlet-mvc_ module to compliment the _scalate-spring-mvc_ one, I not sure how appropriate it would be given that my code doesn't use Spring's view lifecycle. By the same token, it appears to be impossible to extract the ServletConfig without using extensions proprietary to the Portal in use.

Furthermore, it's obviously not appropriate to add this code to _scalate-core_ to live with the original TemplateEngineServlet, as additional dependencies would be dragged in.

I think at the very least I could write up some documentation for this, especially if my code can't be added to Scalate in some way.

Thanks for listening!

&lt;pre&gt;&lt;code&gt;
import javax.servlet.http.{HttpServletRequest, HttpServletResponse}

import org.fusesource.scalate.servlet.TemplateEngineServlet

import org.springframework.web.servlet.ViewRendererServlet
import org.springframework.web.servlet.view.InternalResourceView

/**
 * Allow the TepmlateEngineServlet to be used in a
 * Spring Portlet MVC environment.
 *
 * More specifically, it maps the view path correctly.
 *
 * @author Seb Richards
 */
class TemplateEnginePortletServlet extends TemplateEngineServlet {
	
	override def service(request: HttpServletRequest, response: HttpServletResponse) {
		// Get the view attribute
		val view = request.getAttribute(ViewRendererServlet.VIEW_ATTRIBUTE).asInstanceOf[InternalResourceView];
		
		// Render using the view's URL
		render(view.getUrl, request, response)
	}
	
}
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">2</from-support>
  <id type="integer">5947701</id>
  <importance type="integer">257</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>c2hN7Q1yWr4kLYeJe5cbCb</notification-list>
  <number type="integer">257</number>
  <priority type="integer">4</priority>
  <reporter-id>c2hN7Q1yWr4kLYeJe5cbCb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scalate with Spring Portlet MVC</summary>
  <updated-at type="datetime">2011-09-06T12:46:15-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c2hN7Q1yWr4kLYeJe5cbCb</id><login>sebrichards</login><login_name warning="deprecated">sebrichards</login_name><name>sebrichards</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-09-09T21:09:19-04:00</created-on>
  <description>It would be nice (and hopefully a quick fix) to ensure things like newlines and spaces aren't lost in the presentation of the Exception's message on the error page.</description>
  <from-support type="integer">2</from-support>
  <id type="integer">6264971</id>
  <importance type="integer">262</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>bIvREuUMWr3irVabIlDkbG</notification-list>
  <number type="integer">262</number>
  <priority type="integer">4</priority>
  <reporter-id>bIvREuUMWr3irVabIlDkbG</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Error page does not preserve whitespace formatting from Exception messages</summary>
  <updated-at type="datetime">2011-09-09T21:09:19-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bIvREuUMWr3irVabIlDkbG</id><login>yaaang</login><login_name warning="deprecated">yaaang</login_name><name>Yang Zhang</name><organization>MIT</organization><website>http://yz.mit.edu/</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-10-19T06:24:35-04:00</created-on>
  <description>e.g. something like


&lt;pre&gt;&lt;code&gt;formatNumbers = false

&lt;/code&gt;&lt;/pre&gt;

inside a template or something</description>
  <from-support type="integer">1</from-support>
  <id type="integer">2312165</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">531621</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,bEw1VyeQOr4lzUeJe5cbLr</notification-list>
  <number type="integer">166</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>make it easy to disable the localisation of numbers</summary>
  <updated-at type="datetime">2011-09-10T03:28:56-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>cGhdVOfnqr34N5eJe5afGb</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-12-14T09:03:08-05:00</created-on>
  <description>See this discussion
http://groups.google.com/group/scalate/browse_thread/thread/635033eb1dcc0b23

Note that a workaround is to not quote the expression. So rather than

&lt;pre&gt;&lt;code&gt;
%a(title=&quot;#{blah(&quot;something&quot;)}&quot;)
&lt;/code&gt;&lt;/pre&gt;

Just use the attribute={expression} syntax instead...

&lt;pre&gt;&lt;code&gt;
%a(title={blah(&quot;something&quot;)})
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">2</from-support>
  <id type="integer">2765165</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">531621</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">186</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>dynamic attribute expressions in scaml / jade which are double quote wrapped can't contain String literals</summary>
  <updated-at type="datetime">2011-09-10T03:29:02-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-12-15T04:09:50-05:00</created-on>
  <description>the Scalate filter doesn't detect a URI maps to a folder containing an index.* file matching a template file</description>
  <from-support type="integer">2</from-support>
  <id type="integer">2771121</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">531621</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">187</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scalate filter should map URI &quot;/foo&quot; or &quot;/foo/&quot; for which there is a template called &quot;/foo/index.*&quot; then it should render the template </summary>
  <updated-at type="datetime">2011-09-10T03:29:08-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>duIDmEPaWr350yeJe5cbLA</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">11</component-id>
  <created-on type="datetime">2011-07-19T22:59:58-04:00</created-on>
  <description>comment3, </description>
  <from-support type="integer">1</from-support>
  <id type="integer">4477744</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">531621</milestone-id>
  <notification-list>duIDmEPaWr350yeJe5cbLA</notification-list>
  <number type="integer">250</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>24068</summary>
  <updated-at type="datetime">2011-09-10T03:29:13-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>duIDmEPaWr350yeJe5cbLA</id><login>kengimel</login><login_name warning="deprecated">kengimel</login_name><name>Ikenna Okpala</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-10-25T11:12:58-04:00</created-on>
  <description>e.g. something like this...

&lt;pre&gt;&lt;code&gt;
td(data-bind=&amp;&quot;foo : { ... &gt; 5 .. }&quot;)
&lt;/code&gt;&lt;/pre&gt;

Also I wonder if when using escapeMarkup = false that we should avoid escaping attribute values? Seems this value has no effect right now...
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">8822033</id>
  <importance type="integer">270</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">531621</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">270</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>have a syntax to specify non-escaped attribute values in jade/scaml...</summary>
  <updated-at type="datetime">2011-10-25T11:13:28-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-10-25T11:31:02-04:00</created-on>
  <description></description>
  <from-support type="integer">1</from-support>
  <id type="integer">8823553</id>
  <importance type="integer">271</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">531621</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">271</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>allow &quot;-&quot; in names of attributes when using the ruby style script{ :data-main =&gt; &quot;js/main&quot;} notation in jade/scaml</summary>
  <updated-at type="datetime">2011-10-25T11:31:02-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2011-11-28T06:25:24-05:00</created-on>
  <description></description>
  <from-support type="integer">1</from-support>
  <id type="integer">10535553</id>
  <importance type="integer">275</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">734013</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">275</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>error page should be called Error.* not 500.* as its then easier to reuse on different errors and can be more easily pre-compiled</summary>
  <updated-at type="datetime">2011-11-28T06:25:24-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">0</component-id>
  <created-on type="datetime">2012-03-13T11:05:24-04:00</created-on>
  <description>our ops team raised an issue that Tomcat with our Scalate app deployed is complaining of thread leakage on shutdown. Some investigation has shown that this is the Scala Presentation Compiler thread that is started by Scalate.

I've managed to create a servlet context listener that causes the presentation compiler to shutdown by issuing the following call:

&lt;pre&gt;&lt;code&gt;  
  myTemplateEngine.compiler.asInstanceOf[ScalaCompiler].compiler.askShutdown()
&lt;/code&gt;&lt;/pre&gt;

Works fine, but I'm not really happy with having to cast the Compiler trait and then dig into its internals in order to access the underlying Group instance.
Any chance of adding a shutdown method direct on the Compiler trait? Then I can just issue:

&lt;pre&gt;&lt;code&gt;  
  myTemplateEngine.compiler.shutdown()
&lt;/code&gt;&lt;/pre&gt;

Perhaps also shutdown the compiler as part of the destroy of TemplateEngineFilter (although I'm using Scalate as part of Bowler, so this this isn't as much of an issue for me)?


</description>
  <from-support type="integer">2</from-support>
  <id type="integer">16746833</id>
  <importance type="integer">281</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">734013</milestone-id>
  <notification-list>dPOoieBrSr4BQHacwqjQWU</notification-list>
  <number type="integer">281</number>
  <priority type="integer">3</priority>
  <reporter-id>dPOoieBrSr4BQHacwqjQWU</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Presentation Compiler Shutdown</summary>
  <updated-at type="datetime">2012-03-13T11:05:24-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dPOoieBrSr4BQHacwqjQWU</id><login>skipoleschris</login><login_name warning="deprecated">skipoleschris</login_name><name>skipoleschris</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description>see the discussion here: scalate-commits@googlegroups.com</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203649</id>
  <importance type="integer">11</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,akqxUuVd4r34aqeJe5cbLA</notification-list>
  <number type="integer">1</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>a development time REPL for experimenting with controller/resource/DTO/model objects?</summary>
  <updated-at type="datetime">2010-09-14T11:57:42-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description></description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203653</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">3</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>ant task for pre-compilng scalate templates</summary>
  <updated-at type="datetime">2010-08-24T10:12:20-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description>http://github.com/harrah/browse</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203657</id>
  <importance type="integer">10</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">5</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>generate nice HTML from the source code so folks can browse the code more easily - maybe using SXR?</summary>
  <updated-at type="datetime">2010-08-24T10:12:20-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description>It might be nice to support custom tags using XML markup notation as well. 

This came up on this thread... 
http://old.nabble.com/Re%%3A-JSP-taglibs-in-Scala-p27514294.html 

&lt;pre&gt;&lt;code&gt;
&lt;foo:bar a=&quot;123&quot;&gt;
body
&lt;/foo:bar&gt;
&lt;/code&gt;&lt;/pre&gt;

which would translate to the equivalent of this... 


&lt;pre&gt;&lt;code&gt;
#block( foo.bar(a=&quot;123&quot;) )
body
#end
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203665</id>
  <importance type="integer">9</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">9</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>support the mapping of an XML element to a function invocation in SSP</summary>
  <updated-at type="datetime">2011-01-04T09:38:33-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description></description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203667</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">10</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>the current template compiler depends on the context class loader being a nice behaving URLClassLoader - which fails by default in maven tests. Can we pass just a class loader to Scala compiler?</summary>
  <updated-at type="datetime">2010-08-24T10:12:20-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description>folks might want to create templates using pure XML, using custom tags (mapping namespaces/elements to function calls) and the ${foo} notation for expressions. 

So rather than a custom parser as we have now for SSP, we can have something which parsers the XML and transforms elements based on their namespaces (and looks for ${foo} expressions too). 

We could then process things like this... 

{code} 
 
... 
 
... 
${something} 
... 
 
 
{code} 

which would translate to the equivalent of this in SSP 

{code} 
 
 
... 
 
... 
${something} 
... 
 
 
{code} 
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203671</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">12</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>XML based template engine - like the XML flavour of JSP? (maybe called SXML?)</summary>
  <updated-at type="datetime">2010-08-24T10:12:20-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>cGhdVOfnqr34N5eJe5afGb</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-28T04:22:13-04:00</created-on>
  <description></description>
  <from-support type="integer">1</from-support>
  <id type="integer">1355381</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb</notification-list>
  <number type="integer">83</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>create rpm, deb, pkg for the scalate release for easy install on linux</summary>
  <updated-at type="datetime">2010-11-25T02:48:44-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">1</component-id>
  <created-on type="datetime">2010-05-08T15:07:36-04:00</created-on>
  <description></description>
  <from-support type="integer">0</from-support>
  <id type="integer">1403243</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>bEnPA4onOr35CreJe5d-aX</notification-list>
  <number type="integer">92</number>
  <priority type="integer">3</priority>
  <reporter-id>bEnPA4onOr35CreJe5d-aX</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Document or create an archetype for deploying to GAE</summary>
  <updated-at type="datetime">2010-11-25T02:48:45-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bEnPA4onOr35CreJe5d-aX</id><login>chirino</login><login_name warning="deprecated">chirino</login_name><name>Hiram Chirino</name><website>http://hiramchirino.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-07-06T03:55:59-04:00</created-on>
  <description>I've hit my head on this a few times before - it seemed a bit surprising that &quot; was HTML escaped when generating text in Ssp. I guess the current behaviour is fine, we just need to encourage folks to disable html escaping when generating non-HTML?</description>
  <from-support type="integer">1</from-support>
  <id type="integer">1678581</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list></notification-list>
  <number type="integer">100</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>should &quot; be quoted as &amp;quot; by default?</summary>
  <updated-at type="datetime">2011-03-23T08:05:27-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>bEnPA4onOr35CreJe5d-aX</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-07-24T20:47:08-04:00</created-on>
  <description>requested at: http://groups.google.com/group/scalate/browse_thread/thread/6892a4fbd87bd4b1</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1803043</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>bEnPA4onOr35CreJe5d-aX,akqxUuVd4r34aqeJe5cbLA</notification-list>
  <number type="integer">106</number>
  <priority type="integer">3</priority>
  <reporter-id>bEnPA4onOr35CreJe5d-aX</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Allow templates to extend custom traits</summary>
  <updated-at type="datetime">2010-11-25T02:48:45-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bEnPA4onOr35CreJe5d-aX</id><login>chirino</login><login_name warning="deprecated">chirino</login_name><name>Hiram Chirino</name><website>http://hiramchirino.com</website></assigned-to>
  <reporter><id>bEnPA4onOr35CreJe5d-aX</id><login>chirino</login><login_name warning="deprecated">chirino</login_name><name>Hiram Chirino</name><website>http://hiramchirino.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-07-28T14:53:10-04:00</created-on>
  <description>I think this is mostly due to the classloader loading bytecode finding the classes for the templates in the WEB-INF/classes class loader which is a parent of the new class loader; so it never looks in the tmp directory?</description>
  <from-support type="integer">1</from-support>
  <id type="integer">1819507</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,akqxUuVd4r34aqeJe5cbLA</notification-list>
  <number type="integer">111</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>if you precompile your templates, then deploy your WAR as an expanded WAR - changing templates don't reload</summary>
  <updated-at type="datetime">2010-11-25T02:48:45-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-07-29T14:24:59-04:00</created-on>
  <description>we could support an alternative buffer inside the RenderContext so that when you output a value which is-a Future of some kind

http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html
http://www.scala-lang.org/archives/downloads/distrib/files/nightly/docs/library/scala/actors/Future.html
or Future from Akka etc

then we could provide a different kind of buffer which rather than eagerly converting objects into text, we just store the objects in a ListBuffer[_] or something; then when all of the expressions have been added to the list we then have a separate pass of the List[_] converting all objects to Strings; which in the case of a Future we'd do a get to block.

We could then have a completely async code generator, where all expressions are evaluated asynchronously, wrapping the expressions in some syntax; or we could use some actor library to make expressions async (creating a Future for the expression), or using something like HawtDispatch - so folks can choose exactly which expressions should be evaluated async - or the domain services themselves could just return Future[T] instead, hiding the async stuff from the templates completely.

http://hawtdispatch.fusesource.org/

e.g. in a template

{{{
    some text ${^{foo.someRemoteInvocation}} some text ${x + 5}
}}}


</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1824727</id>
  <importance type="integer">113</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,akqxUuVd4r34aqeJe5cbLA</notification-list>
  <number type="integer">113</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>support for async/future expressions?</summary>
  <updated-at type="datetime">2010-09-14T11:57:59-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-07-30T07:23:52-04:00</created-on>
  <description>we should consider supporting $foo(blah) or $foo() as valid expressions to avoid the noisy ${foo(1234)}. Particularly as ) followed by } is easy to mess up and hard to read.

I guess $foo could be a little dangerous - though I guess folks can escape with $$</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1827551</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list></notification-list>
  <number type="integer">117</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>SSP expressions which are function calls or identifiers could avoid the {}</summary>
  <updated-at type="datetime">2011-03-04T03:41:25-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-08-25T00:23:01-04:00</created-on>
  <description>see this thread for more details...

http://groups.google.com/group/scalate/browse_thread/thread/5a98606562b4b048</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1997749</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,at76nGtaCr4iX2eJe5cbLr</notification-list>
  <number type="integer">142</number>
  <priority type="integer">3</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>support compiling templates on the fly inside OSGi</summary>
  <updated-at type="datetime">2012-01-29T18:55:20-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">10</component-id>
  <created-on type="datetime">2011-11-26T20:16:50-05:00</created-on>
  <description>Scalate Mustache implementation shouldn't escape plain text, specially plain text inside of &lt;script&gt;,&lt;style&gt; html sections. and must honor the {{{ }}} or {{&amp; }} expressions always.

*Example 1:*
&lt;pre&gt;&lt;code&gt;
 &lt;script type=&quot;text/javascript&quot;&gt;
    alert(&quot;Always escaped&quot;);
&lt;/script&gt;
&lt;/code&gt;&lt;/pre&gt;
*Actual output:*
&lt;pre&gt;&lt;code&gt;
 &lt;script type=&quot;text/javascript&quot;&gt;
    alert(&amp;quot;Always escaped&amp;quot;);
&lt;/script&gt;
&lt;/code&gt;&lt;/pre&gt;
*Expected output:*
&lt;pre&gt;&lt;code&gt;
 &lt;script type=&quot;text/javascript&quot;&gt;
    alert(&quot;Always escaped&quot;);
&lt;/script&gt;
&lt;/code&gt;&lt;/pre&gt;

*Example 2*: data={&quot;name&quot;: &quot;Joe&quot;};
&lt;pre&gt;&lt;code&gt;
&lt;script type=&quot;text/javascript&quot;&gt;
    var initData = {{{data}}};
&lt;/script&gt;
&lt;/code&gt;&lt;/pre&gt;
*Actual output:*
&lt;pre&gt;&lt;code&gt;
&lt;script type=&quot;text/javascript&quot;&gt;
    var initData = {&amp;quot;name&amp;quot;:&amp;quot;John&amp;quot;};
&lt;/script&gt;
&lt;/code&gt;&lt;/pre&gt;
*Expected output:*
&lt;pre&gt;&lt;code&gt;
&lt;script type=&quot;text/javascript&quot;&gt;
    var initData = {&quot;name&quot;:&quot;John&quot;};
&lt;/script&gt;
&lt;/code&gt;&lt;/pre&gt;

For more information and possible patch/fix check these two discussions:
[[url:https://groups.google.com/forum/#!searchin/scalate/mustache/scalate/Au1I_0W1ZTs/-5WXDczVMH4J|Javascript is escaped while using mustache layout mechanism]]
[[url:https://groups.google.com/forum/#!searchin/scalate/mustache/scalate/9XxouO1bLLI/pu5k1XhzYOcJ|Mustache unescape HTML]]</description>
  <from-support type="integer">2</from-support>
  <id type="integer">10500633</id>
  <importance type="integer">274</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>aTRsWYgi8r4zpQacwqjQYw</notification-list>
  <number type="integer">274</number>
  <priority type="integer">3</priority>
  <reporter-id>aTRsWYgi8r4zpQacwqjQYw</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scalate Mustache shouldn't escape plain text under &lt;script&gt;, &lt;style&gt; html elements and must honor {{{}}} {{&amp;}} expresions</summary>
  <updated-at type="datetime">2011-11-28T17:50:50-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aTRsWYgi8r4zpQacwqjQYw</id><login>espina.edgar</login><login_name warning="deprecated">espina.edgar</login_name><name>espina.edgar</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description>Scaml is applying filters at runtime. If no interpolation is being done, then the filter input is a string litteral, it might make more sense to run the filter at compile time against the litteral and compile in the filter result so that it does not need to get executed a runtime. 

But since a filter could be dynamic (inserting stuff like the current date or a counter), then this optimization would need some kind of hint to know if it can be performed.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203757</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>bEnPA4onOr35CreJe5d-aX</notification-list>
  <number type="integer">55</number>
  <priority type="integer">4</priority>
  <reporter-id>bEnPA4onOr35CreJe5d-aX</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scaml: Apply as many filters as possible at compile time</summary>
  <updated-at type="datetime">2010-11-25T02:48:44-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bEnPA4onOr35CreJe5d-aX</id><login>chirino</login><login_name warning="deprecated">chirino</login_name><name>Hiram Chirino</name><website>http://hiramchirino.com</website></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-02-24T04:12:04-05:00</created-on>
  <description>Jade/Scaml supports nice expressions like
&lt;pre&gt;&lt;code&gt;a(href=myLink)
 some text
&lt;/code&gt;&lt;/pre&gt;
which is equivalent to 
&lt;pre&gt;&lt;code&gt;a(href={myLink})
 some text
&lt;/code&gt;&lt;/pre&gt;
though since its so common to want to use the uri function to normalise links, it'd be nice to be able to do
&lt;pre&gt;&lt;code&gt;a(href=uri(&quot;/foo&quot;))
 some text
&lt;/code&gt;&lt;/pre&gt;
instead of the more verbose
&lt;pre&gt;&lt;code&gt;a(href={uri(&quot;/foo&quot;)})
 some text
&lt;/code&gt;&lt;/pre&gt;
i.e. the parser for an attribute value would just have to look for: identifier &lt;~ &quot;(&quot; and if so eat all the text up to &quot;)&quot; and decide its an expression</description>
  <from-support type="integer">2</from-support>
  <id type="integer">3213187</id>
  <importance type="integer">218</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>cGhdVOfnqr34N5eJe5afGb,bEw1VyeQOr4lzUeJe5cbLr</notification-list>
  <number type="integer">218</number>
  <priority type="integer">4</priority>
  <reporter-id>cGhdVOfnqr34N5eJe5afGb</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>would be nice in jade/scaml that attribute values could be function calls without requiring {} wrapper</summary>
  <updated-at type="datetime">2011-11-11T09:00:57-05:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cGhdVOfnqr34N5eJe5afGb</id><login>jstrachan</login><login_name warning="deprecated">jstrachan</login_name><name>jstrachan</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-04-02T08:20:29-04:00</created-on>
  <description></description>
  <from-support type="integer">0</from-support>
  <id type="integer">1203767</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">191835</milestone-id>
  <notification-list>bEnPA4onOr35CreJe5d-aX</notification-list>
  <number type="integer">60</number>
  <priority type="integer">5</priority>
  <reporter-id>bEnPA4onOr35CreJe5d-aX</reporter-id>
  <space-id>ch1oPQonOr37aXeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Scaml: Object References</summary>
  <updated-at type="datetime">2010-08-24T10:12:22-04:00</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bEnPA4onOr35CreJe5d-aX</id><login>chirino</login><login_name warning="deprecated">chirino</login_name><name>Hiram Chirino</name><website>http://hiramchirino.com</website></reporter>
</ticket>
</tickets>

