<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Thu May 23 13:44:01 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-55/DCOM-55.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-55] Ugly problems with default import __NAMESPACE__ when it contains non-annotation classes that are docblock props</title>
                <link>http://www.doctrine-project.org/jira/browse/DCOM-55</link>
                <project id="10043" key="DCOM">Doctrine Common</project>
                        <description>&lt;p&gt;Say you have a class &quot;Entity&quot;.&lt;/p&gt;

&lt;p&gt;Then /** @Entity */ on a class in the same namespace will try to instantiate Entity.&lt;/p&gt;

&lt;p&gt;We should avoid this by testing if Entity is a subclass of  \Doctrine\Common\Annotations\Annotation&lt;/p&gt;</description>
                <environment></environment>
            <key id="12764">DCOM-55</key>
            <summary>Ugly problems with default import __NAMESPACE__ when it contains non-annotation classes that are docblock props</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="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="beberlei">Benjamin Eberlei</reporter>
                        <labels>
                    </labels>
                <created>Wed, 29 Jun 2011 21:10:34 +0000</created>
                <updated>Wed, 29 Jun 2011 22:01:14 +0000</updated>
                    <resolved>Wed, 29 Jun 2011 22:01:14 +0000</resolved>
                            <version>2.1</version>
                                <fixVersion>2.1</fixVersion>
                                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="16098" author="beberlei" created="Wed, 29 Jun 2011 21:55:31 +0000"  >&lt;p&gt;Actually this problem is more problematic, we have to enforce extending \Doctrine\Common\Annotations\Annotation for ALL annotations.&lt;/p&gt;</comment>
                    <comment id="16099" author="beberlei" created="Wed, 29 Jun 2011 22:01:14 +0000"  >&lt;p&gt;Fixed.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>