<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Thu May 23 08:21:27 UTC 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.doctrine-project.org/jira/si/jira.issueviews:issue-xml/DCOM-118/DCOM-118.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Doctrine Project</title>
    <link>http://www.doctrine-project.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.7</version>
        <build-number>850</build-number>
        <build-date>21-02-2013</build-date>
    </build-info>

<item>
            <title>[DCOM-118] [GH-195] Add failing test to demonstrate parse error when @ is present in the description</title>
                <link>http://www.doctrine-project.org/jira/browse/DCOM-118</link>
                <project id="10043" key="DCOM">Doctrine Common</project>
                        <description>&lt;p&gt;This issue is created automatically through a Github pull request on behalf of Seldaek:&lt;/p&gt;

&lt;p&gt;  Url: &lt;a href=&quot;https://github.com/doctrine/common/pull/195&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/common/pull/195&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Message:&lt;/p&gt;

&lt;p&gt;If someone can take this and fix the issue it&apos;d be great. I couldn&apos;t figure it out at a quick glance and I don&apos;t really have time, but it&apos;s a pretty messed up bug and not so trivial to debug if you don&apos;t know what happens in the background so I&apos;d say it&apos;s pretty important.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14086">DCOM-118</key>
            <summary>[GH-195] Add failing test to demonstrate parse error when @ is present in the description</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="beberlei">Benjamin Eberlei</reporter>
                        <labels>
                    </labels>
                <created>Tue, 2 Oct 2012 15:19:06 +0000</created>
                <updated>Wed, 3 Oct 2012 04:27:17 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="18759" author="psc" created="Tue, 2 Oct 2012 17:35:51 +0000"  >&lt;p&gt;I digged a little deeper. The test case is a great one &lt;img class=&quot;emoticon&quot; src=&quot;http://www.doctrine-project.org/jira/images/icons/emoticons/smile.gif&quot; height=&quot;20&quot; width=&quot;20&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;br/&gt;
The DocLexer cuts ut -1 position from the first @ (which is the @ in the @example.com). so that the lexer has to process:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
o@example.com&quot;
     * }
     *
     * @AnnotationTargetPropertyMethod(&lt;span class=&quot;code-quote&quot;&gt;&quot;Bar&quot;&lt;/span&gt;)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;So that the catchable pattern: (&quot;(?:&lt;span class=&quot;error&quot;&gt;&amp;#91;^&amp;quot;&amp;#93;&lt;/span&gt;|&quot;&quot;)*&quot;) matches here to greedy (it matches string in quotes):&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&quot;
     * }
     *
     * @AnnotationTargetPropertyMethod(&quot;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;As a result the lexer does not catch the correct @ from the Annotation&lt;/p&gt;

&lt;p&gt;I could not think of a fast fix for this. But maybe tomorrow.&lt;br/&gt;
(leaving quoted string pattern with an @ was a wrong idea)&lt;/p&gt;

&lt;p&gt;Its not a workaround to do more or less cutting in the parser, because not-well-formed quoted strings would break anyway&lt;/p&gt;</comment>
                    <comment id="18761" author="psc" created="Wed, 3 Oct 2012 04:27:17 +0000"  >&lt;p&gt;can someone think of a case, where a string (in some annotation) has a newline in it? Otherwise the tests do not fail, when I leave the string matching pattern with a newline.&lt;br/&gt;
I still had another idea to restrict the position of a annotation more strictly to:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;the beginning of a new line (\s*&amp;#42;\s* before)&lt;/li&gt;
	&lt;li&gt;in another annotation&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;but the second is not solvable with the lexer itself and would transfer the quoted string matching to the parser, because it needs context.&lt;/p&gt;

&lt;p&gt;I&apos;ll let seldaek pull, what I have (is this the right way?)&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>